From: Sebastian Moeller <moeller0@gmx.de>
To: "Kevin Darbyshire-Bryant" <kevin@darbyshire-bryant.me.uk>,
"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, 01 Jun 2016 13:57:47 +0200 [thread overview]
Message-ID: <0026A232-9D17-40FD-83A4-8575C6FFB8C3@gmx.de> (raw)
In-Reply-To: <574ECB5E.7090605@darbyshire-bryant.me.uk>
Hi Kevin
On June 1, 2016 1:47:42 PM GMT+02:00, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
>
>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?
At least on ingress that is all we can do right now, as the iptables gets only run after the intermediate functional block device. So we can explicitly not do what we like, that is to use iptables to re-mapp DSCP marks to our internal liking and then have these Interpreten to select the correct priority tin... Re-map all to 0 is just a special case of that...
Best Regards
Sebastian
>
>Kevin
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2016-06-01 11:57 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
2016-06-01 11:57 ` Sebastian Moeller [this message]
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=0026A232-9D17-40FD-83A4-8575C6FFB8C3@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
--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