From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: moeller0 <moeller0@gmx.de>, "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [lede-project/source] Add support for cake qdisc (#72)
Date: Wed, 1 Jun 2016 12:47:42 +0100 [thread overview]
Message-ID: <574ECB5E.7090605@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <D7CE2141-1157-4453-BC8C-886F9316FFD9@gmx.de>
On 01/06/16 12:41, moeller0 wrote:
> Hi Toke,
>> I'm guessing this was probably discussed before and I've simply
>> forgotten; but why does this (rewriting dscp bits) need to be part of
>> the qdisc when you can do it with iptables?
>
> Well, cake looks at the DSCP bits already, if it can do the re-mapping we potentially would not need to touch iptables at all, which cakes goal being simplicity seemed on-focus. But since this feature turned out to be contentious, I vote for throwing it out and just rely on iptables… I believe Jonathan argued that the re-mapping really is an orthogonal issue that does not conceptually belong into a qdisc, a valid points as by now everyone agrees…
>
> Best Regards
> Sebastian
One silly question from ignorant fool: Can you do the iptables DSCP
remapping in such a way that the qdisc still sees/prioritize based on
them but clear/remap on output?
Kevin
next prev parent reply other threads:[~2016-06-01 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <lede-project/source/pull/72@github.com>
[not found] ` <lede-project/source/pull/72/c222782884@github.com>
2016-06-01 10:02 ` Kevin Darbyshire-Bryant
2016-06-01 10:13 ` Dave Täht
2016-06-01 10:20 ` Kevin Darbyshire-Bryant
2016-06-01 10:52 ` moeller0
2016-06-01 11:20 ` Toke Høiland-Jørgensen
2016-06-01 11:41 ` moeller0
2016-06-01 11:47 ` Kevin Darbyshire-Bryant [this message]
2016-06-01 11:57 ` Sebastian Moeller
2016-06-01 12:25 ` Benjamin Cronce
2016-06-01 13:09 ` Kevin Darbyshire-Bryant
2016-06-01 13:51 ` Jonathan Morton
2016-06-01 15:19 ` moeller0
2016-06-01 20:22 ` David Lang
2016-06-01 15:26 ` Dave Taht
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=574ECB5E.7090605@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=toke@toke.dk \
/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