From: Dave Taht <dave.taht@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow_hash vs host_hash
Date: Mon, 5 Oct 2015 16:01:52 +0200 [thread overview]
Message-ID: <CAA93jw6Cxs-tbuKB7GD0CDB0q0vr5pAwNezZoHp=CG=bQUmExw@mail.gmail.com> (raw)
In-Reply-To: <0EB23696-5866-48C5-AC7E-B8570C7AA900@gmx.de>
I would like the dual-flow pony in this net-next merge window please.
Otherwise I am sore inclined to get what we have out there! I hope to
get the api and abi changes in today or tomorrow for the bits I
understand....
On Mon, Oct 5, 2015 at 2:45 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> Hi Jonathan,
>
> On Oct 5, 2015, at 14:30 , Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> It's a precursor to the dual host/flow isolation, which I'm still working on.
>
> I believe that this is the single most asked-for feature in the openwrt forums, people somehow want to enforce per internal-IP fairness. I am not sure whether all/most people actually need this, since only a few have tries pure flow-isolation before declaring per-internal-SRC-IP fairness a requirement. But once this is in (and we get cake into openwrt default builds), you will have saved a considerable amount of people gray hair ;) Just to be clear, I am a huge cake fan (despite my occasionally sceptic emails about obscure side issues) and hope with the dual isolation cake will offer almost everything a typical user might actually want (well, except the ponies)
>
> 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
next prev parent reply other threads:[~2015-10-05 14:01 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 [this message]
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
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='CAA93jw6Cxs-tbuKB7GD0CDB0q0vr5pAwNezZoHp=CG=bQUmExw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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