Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: John Sager <john@sager.me.uk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] conntrack lookup continuation
Date: Fri, 3 Feb 2017 21:30:16 +0200	[thread overview]
Message-ID: <D48BB380-2EFB-4BDA-A8FF-4874048976EB@gmail.com> (raw)
In-Reply-To: <f3b1747f-8ace-4fe5-b160-3d6440df5f92@sager.me.uk>


> On 3 Feb, 2017, at 21:01, John Sager <john@sager.me.uk> wrote:
> 
> As cake uses diffserv to classify, it would be good to carry dscp in the
> conntrack & transfer it to incoming packets with an 'action' on the ingress
> filter, but carrying dscp specifically in the conntrack record would be
> quite a significant change to other parts of linux. Hence the use of fwmark
> and the conntrack mark field, which already exist.

Yes, this is what I thought you meant.

As fwmark just sets “a number” on the conntrack record, there’s no reason in principle not to have that number be a DSCP (or some reasonably transformed representation of one).  The trick is then for cake to extract that number from the conntrack record (having looked it up), and if it looks valid, to use it as the packet’s DSCP instead of the one on the packet itself.

In principle, that should not be difficult.  For the moment however, I’ve got my hands full with writing a report on performance tests I’ve been running, and then getting reacquainted with some code changes that happened while I was looking elsewhere.

 - Jonathan Morton


  reply	other threads:[~2017-02-03 19:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 14:49 Felix Resch
2017-01-31 21:14 ` Jonathan Morton
2017-02-03 16:42   ` John Sager
2017-02-03 17:08     ` Dave Taht
2017-02-03 19:01       ` John Sager
2017-02-03 19:30         ` Jonathan Morton [this message]
2017-02-03 21:25           ` John Sager
2017-02-04  5:51         ` Konstantin Shalygin
2017-02-04  9:12           ` John Sager

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=D48BB380-2EFB-4BDA-A8FF-4874048976EB@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=john@sager.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