Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] act_conndscp
Date: Fri, 22 Mar 2019 21:24:27 +0000	[thread overview]
Message-ID: <F071FAE8-C93C-4E20-94EE-9D7C8DDC0ED6@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <F9C19E7B-ECA7-4A54-8533-D3F3B34DA806@darbyshire-bryant.me.uk>

It looks like act_conndscp has been shot down by the kernel people, at least in its current form.  Setting a conntrack mark from tc is regarded as “not sure if it is a good idea”.  The other way (conntrack to skb) is fine.  That’s sort of good news in that ingress is the hard bit as it’s problematic with iptables.

egress is within iptables coverage - ‘just’ need a way to store a DSCP & flag to conntrack mark.


Cheers,

Kevin D-B

gpg: 012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A


  reply	other threads:[~2019-03-22 21:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 20:08 Kevin Darbyshire-Bryant
2019-03-19 21:24 ` Ryan Mounce
2019-03-19 21:27   ` Kevin Darbyshire-Bryant
2019-03-19 21:41     ` Toke Høiland-Jørgensen
2019-03-19 21:51       ` Kevin Darbyshire-Bryant
2019-03-19 21:59         ` Toke Høiland-Jørgensen
2019-03-20  3:31     ` Ryan Mounce
2019-03-20  8:25       ` Kevin Darbyshire-Bryant
2019-03-20  8:38         ` Sebastian Moeller
2019-03-20  9:01           ` Kevin Darbyshire-Bryant
2019-03-20  9:54             ` Sebastian Moeller
2019-03-20 10:15               ` Kevin Darbyshire-Bryant
2019-03-22 21:24                 ` Kevin Darbyshire-Bryant [this message]
2019-03-23 18:35                   ` Kevin Darbyshire-Bryant
2019-04-01 14:07                     ` Kevin Darbyshire-Bryant
2019-04-01 23:52                       ` Ryan Mounce
2019-03-20  9:06           ` Kevin Darbyshire-Bryant
2019-03-20  9:24             ` Kevin Darbyshire-Bryant

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=F071FAE8-C93C-4E20-94EE-9D7C8DDC0ED6@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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