From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Possible conntrack lookup improvements
Date: Fri, 3 May 2019 19:23:17 +0000 [thread overview]
Message-ID: <0D8001E5-0B7B-44BD-914A-B3F41E0558D0@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <87h8abgxmi.fsf@toke.dk>
> On 3 May 2019, at 20:13, Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
> Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
>
>>> On 3 May 2019, at 15:16, Jonathan Morton <chromatix99@gmail.com> wrote:
>>>
>>>> On 3 May, 2019, at 4:55 pm, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>>>>
>>>> Two patches attached - one is a simple variable elimination with no functional change. The second changes/simplifies the conntrack tuple lookup & usage. I’ve had a play and I don’t think I’ve broken any of the host fairness BUT it could do with some more testing, that’s where you come in…
>>>
>>> Looks like sound logic, as long as it does actually work. It could be a useful speedup for those small CPE devices which need NAT and host-fairness working.
>>
>> It’s interesting you bring that up - are we sure that ingress host NAT
>> fairness works in the upstream kernel version of CAKE anyway? I’m
>> looking at cake_update_flowkeys(…) and thinking half of it is missing?
>
> No, it's just moved into nf_conntrack_get_tuple_skb(); this was part of
> the work we did to ensure sch_cake could load without a dependency on
> the conntrack module...
>
> It does carry over the 'nf_ct_tuple(ct, !hash->tuple.dst.dir);' and the
> subsequent reversion, though, but I think the logic fits what's in the
> out-of-tree version?
>
> -Toke
Ahh! yes I see, thanks. - elixir or my ability to operate elixir was failing earlier.
Yes and agree the logic follows the out-of-tree…and I can see how my change to it would be applied, assuming it does actually work.
Cheers,
Kevin D-B
gpg: 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
next prev parent reply other threads:[~2019-05-03 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 13:55 Kevin Darbyshire-Bryant
2019-05-03 14:16 ` Jonathan Morton
2019-05-03 18:57 ` Kevin Darbyshire-Bryant
2019-05-03 19:13 ` Toke Høiland-Jørgensen
2019-05-03 19:23 ` Kevin Darbyshire-Bryant [this message]
2019-05-03 23:57 ` Kevin Darbyshire-Bryant
2019-05-03 14:22 ` Toke Høiland-Jørgensen
2019-05-03 14:32 ` Kevin Darbyshire-Bryant
2019-05-03 15:13 ` Toke Høiland-Jørgensen
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=0D8001E5-0B7B-44BD-914A-B3F41E0558D0@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=toke@redhat.com \
/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