From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow_hash vs host_hash
Date: Tue, 6 Oct 2015 12:59:47 +0200 [thread overview]
Message-ID: <46314F4D-74CA-4E3B-9F92-63F8A4136C9B@gmx.de> (raw)
In-Reply-To: <40678341-B798-4832-95E5-2659E0EF24D2@gmail.com>
Hi Jonathan,
On Oct 6, 2015, at 10:44 , Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 6 Oct, 2015, at 11:39, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>
>> Sebastian Moeller <moeller0@gmx.de> writes:
>>
>>> Ah, I see. I guess you are right, but on egress we could get back to
>>> the pre-nat addresses, like Vincent does in nxt_routed_hfsc.qos?
>
> I can’t immediately see how that works.
>
>> Ah, so there is a hook to get those; cool. Just need to make sure Cake
>> uses that, then :)
>
> I think the better solution would be to implement that in the flow dissector. Then Cake (and all other relevant qdiscs) will receive that information automatically.
Certainly. But all of this hopefully does impede the implementation of the dual-flow-classifiying cake-mode; as even without those refinements the dual-mode should work well for IPv6 (assuming people do not game this by using excessive amounts of addresses per host) and non-NATed IPv4…
Best Regards
Sebastian
>
> - Jonathan Morton
>
next prev parent reply other threads:[~2015-10-06 10:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 12:20 Dave Taht
2015-10-05 12:30 ` Jonathan Morton
2015-10-05 12:45 ` Sebastian Moeller
2015-10-05 14:01 ` Dave Taht
2015-10-06 6:26 ` Kevin Darbyshire-Bryant
2015-10-06 7:18 ` Sebastian Moeller
2015-10-06 8:13 ` Toke Høiland-Jørgensen
2015-10-06 8:27 ` Sebastian Moeller
2015-10-06 8:28 ` Toke Høiland-Jørgensen
2015-10-06 8:37 ` Sebastian Moeller
2015-10-06 8:39 ` Toke Høiland-Jørgensen
2015-10-06 8:44 ` Jonathan Morton
2015-10-06 10:59 ` Sebastian Moeller [this message]
2015-10-06 12:51 ` Dave Taht
2015-10-06 13:56 ` Jonathan Morton
2015-10-06 15:07 ` David Lang
2015-10-06 9:38 ` Sebastian Moeller
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=46314F4D-74CA-4E3B-9F92-63F8A4136C9B@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.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