Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow dissector idea/enhancement - help
Date: Thu, 2 Jun 2016 15:29:14 +0300	[thread overview]
Message-ID: <6A7C70EE-906E-4624-A84A-645ED4530A07@gmail.com> (raw)
In-Reply-To: <57501404.5010704@darbyshire-bryant.me.uk>


> On 2 Jun, 2016, at 14:09, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> 
> Cake uses the flow dissector API to do flow hashing...including per host flows for dual/triple isolation.  The unfortunate bit is that the qdisc inevitably gets placed after packets have been NATed on egress and before they've been de-NATed on ingress.
> 
> When mentioned before Johnathan said "flow dissector ideally needs to be tweaked to do this" or words to that effect.
> 
> I'd like to progress that idea...the thought of me kernel programming should horrify everyone but really I'm asking for help in being pointed in the right direction to ask for help...and go from there :-)

I believe Linux does NAT using a “connection tracker” subsystem.  That would contain the necessary data for resolving NAT equivalents.  I don’t know how easy it is to query in a qdisc context, though.

 - Jonathan Morton


  reply	other threads:[~2016-06-02 12:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 11:09 Kevin Darbyshire-Bryant
2016-06-02 12:29 ` Jonathan Morton [this message]
2016-06-30  9:33   ` Kevin Darbyshire-Bryant
2016-06-30 10:27     ` Jonathan Morton
2016-06-30 19:23       ` Kevin Darbyshire-Bryant
2016-07-01  8:11         ` Kevin Darbyshire-Bryant
2016-07-01 15:38           ` Kevin Darbyshire-Bryant
2016-07-02 12:47     ` [Cake] conntrack and ipv6 Dave Täht
2016-07-02 13:00       ` moeller0
2016-07-03  6:16       ` David Lang
2016-07-03  7:44         ` Jonathan Morton
2016-07-03 21:12       ` [Cake] [Cerowrt-devel] " moeller0

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=6A7C70EE-906E-4624-A84A-645ED4530A07@gmail.com \
    --to=chromatix99@gmail.com \
    --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