Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow_hash vs host_hash
Date: Tue, 6 Oct 2015 09:18:22 +0200	[thread overview]
Message-ID: <0F1BBA35-381C-4405-967A-3E266CFCC6F1@gmx.de> (raw)
In-Reply-To: <561369A9.2090607@darbyshire-bryant.me.uk>

Hi Kevin,

On Oct 6, 2015, at 08:26 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:

> 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.

	I believe you nailed it, but the pony will still work on egress, and a sufficiently motivated user can instantiate sqm on an inward facing interface so that the real ingress (from the users perspective) will be processed after NAT. Also as you allude to IPv6 should work out of the box. I believe there were rumblings on net-dev to hook up iptables with the ingress qdisc, which in the long run might allow to get the de-NATed addresses from packets arriving on an IFB device (or it might not, who knows ;) ). In any case we should write up some documentation about the expected behavior and configuration options for the dual-isolation option, once it lands...

Best Regards
	Sebastian


> 
> 
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


  reply	other threads:[~2015-10-06  7:18 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 [this message]
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=0F1BBA35-381C-4405-967A-3E266CFCC6F1@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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