From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] squash option
Date: Mon, 13 Apr 2015 03:01:42 +0300 [thread overview]
Message-ID: <DB649488-4433-4FD6-A569-932BC08F444F@gmail.com> (raw)
In-Reply-To: <CAA93jw507rz1qQWzVacGnxmrc1Ga9pFOn_S7bjVHcnROW7jqBw@mail.gmail.com>
> On 13 Apr, 2015, at 01:20, Dave Taht <dave.taht@gmail.com> wrote:
>
> Inbound diffserv markings cannot be trusted. A simple remark to
> dscp & ECT(3) of diffserv is kind of a must for cake.
As I noted previously, cake can trivially be configured to ignore Diffserv. A simple iptables rule would then suffice to remove the mark for downstream consumers if desired.
More useful would be the ability to re-mark packets according to local Diffserv policy before cake’s classifier acts on it. Iptables doesn’t help here, because it runs *after* ingress qdiscs (even in ifb). Unfortunately, the likely complexity of the configuration mechanism for such a device runs counter to cake’s deliberately simple configuration interface.
However, I have no objection to a second qdisc which could be run in series with cake to perform that function. This would be a qdisc which performs no queueing of its own, and simply performs the re-marking before passing the packet up the qdisc stack. The configuration mechanism of this can be relatively complex, but narrowly focused on the re-marking task. Call it “icing” or “cherry” or whatever, to emphasise that it goes on top of cake.
- Jonathan Morton
next prev parent reply other threads:[~2015-04-13 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 22:20 Dave Taht
2015-04-13 0:01 ` Jonathan Morton [this message]
2015-04-13 15:30 ` 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=DB649488-4433-4FD6-A569-932BC08F444F@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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