From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow_hash vs host_hash
Date: Tue, 6 Oct 2015 08:07:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1510060805260.2943@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw7xmmzJJfLSw2=qiEqDhBad2-TFcWHqdF92xomLrMs2kQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2245 bytes --]
only if the bottleneck router that needs to do the queuing is directly adjacent
to the endpoints.
Yes, home routers commonly fit this definition, but since the usual case is a
router/modem from the ISP with a wifi router plugged into it and the endpoints
attached to the wifi router (wired or wireless), the ISP router/modem which has
the actual bottleneck and should be doing the queuing isn't going to actually
see the endpoint mac addresses.
David Lang
On Tue, 6 Oct 2015, Dave Taht wrote:
> In most scenarios the top level hash for per station queuing on
> ethernet would be
> source or destination macaddr, thus bypassing ipv4 or ipv6.
>
> Then below that goes the 5 tuple.
>
> On Tue, Oct 6, 2015 at 12:59 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>> 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
>>>
>>
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>
>
>
> --
> Dave Täht
> Do you want faster, better, wifi? https://www.patreon.com/dtaht
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2015-10-06 15:08 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
2015-10-06 12:51 ` Dave Taht
2015-10-06 13:56 ` Jonathan Morton
2015-10-06 15:07 ` David Lang [this message]
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=alpine.DEB.2.02.1510060805260.2943@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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