From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] flow_hash vs host_hash
Date: Tue, 6 Oct 2015 07:26:49 +0100 [thread overview]
Message-ID: <561369A9.2090607@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw6Cxs-tbuKB7GD0CDB0q0vr5pAwNezZoHp=CG=bQUmExw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On 05/10/15 15:01, Dave Taht wrote:
> 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....
>
The view that it should just get out there has already been expressed.
Silly question time (IPv4): This dual flow host isolation pony, how will
it work on the WAN facing link on a 'domestic' router when the WAN side
is post NAT. Won't the ip source address just be the router's external
interface? But let this question not distract from proper coding not
the semi-intelligent cut'n'paste stuff that I do.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-10-06 6:27 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 [this message]
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=561369A9.2090607@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
/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