[Cake] flow_hash vs host_hash
dave.taht at gmail.com
Tue Oct 6 08:51:46 EDT 2015
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 at gmx.de> wrote:
> Hi Jonathan,
> On Oct 6, 2015, at 10:44 , Jonathan Morton <chromatix99 at gmail.com> wrote:
>>> On 6 Oct, 2015, at 11:39, Toke Høiland-Jørgensen <toke at toke.dk> wrote:
>>> Sebastian Moeller <moeller0 at 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
>> - Jonathan Morton
> Cake mailing list
> Cake at lists.bufferbloat.net
Do you want faster, better, wifi? https://www.patreon.com/dtaht
More information about the Cake