From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] allocate_src allocate_dst
Date: Sat, 25 Nov 2017 17:28:29 +0100 [thread overview]
Message-ID: <0D923D70-F9A2-4CB9-A516-B6B80FF4967B@gmail.com> (raw)
In-Reply-To: <840D255A-5723-4D95-BEF3-50B411A7D0E8@darbyshire-bryant.me.uk>
> On Nov 25, 2017, at 3:08 PM, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
>> On 25 Nov 2017, at 03:59, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> there is no place in the current code base where these are not both
>> true or both false. Thus redundant.
>>
>> ?
>
> Yes, interesting that. Been there since introduced in 5a6da2ba Add triple-isolation support. *EXPERIMENTAL*
>
> Have done a PR https://github.com/dtaht/sch_cake/pull/72 with a minor cleanup for that - been running on my router with no explosions :-)
Woah, nice find. I’d been working through that function (looking at setting srchost_hash and dsthost_hash to a packet mark value for custom isolation) and between the gotos and ifdefs for kernel version support, it takes some work to look at it.
Could this function be refactored a bit for readability? I’d offer to do it, but this is an important piece of code with little room for error and more ways to plant hard to find problems, better played with by someone who’s more familiar with it...
next prev parent reply other threads:[~2017-11-25 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 3:59 Dave Taht
2017-11-25 14:08 ` Kevin Darbyshire-Bryant
2017-11-25 15:19 ` Jonathan Morton
2017-11-25 16:36 ` Kevin Darbyshire-Bryant
2017-11-25 16:41 ` Jonathan Morton
2017-11-25 16:43 ` Kevin Darbyshire-Bryant
2017-11-25 16:46 ` Dave Taht
2017-11-25 17:07 ` Kevin Darbyshire-Bryant
2017-11-25 16:45 ` Dave Taht
2017-11-25 16:52 ` Dave Taht
2017-11-25 16:58 ` Dave Taht
2017-11-25 16:28 ` Pete Heist [this message]
[not found] ` <CAJq5cE1haW1AqfECJws1DF=AUGxoRar-5ODSPxv=pLRyGTABWg@mail.gmail.com>
[not found] ` <CAJq5cE1Rvz_Oa94kbfouoniZYtcK4qB5gtL1JngsZ_XdTnpQxw@mail.gmail.com>
2017-11-25 16:32 ` Jonathan Morton
2017-11-25 16:48 ` Dave Taht
2017-11-25 18:48 ` Pete Heist
[not found] ` <CAJq5cE15hirznu_Zhbr_om-+_s9T7YF+OKag4MQPW7iz7Bzn_Q@mail.gmail.com>
2017-11-25 19:04 ` Jonathan Morton
2017-11-25 20:03 ` George Amanakis
2017-11-25 20:49 ` Kevin Darbyshire-Bryant
2017-11-25 21:20 ` Kevin Darbyshire-Bryant
2017-11-26 10:19 ` Kevin Darbyshire-Bryant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0D923D70-F9A2-4CB9-A516-B6B80FF4967B@gmail.com \
--to=peteheist@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=kevin@darbyshire-bryant.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox