From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] squash option
Date: Mon, 13 Apr 2015 08:30:20 -0700 [thread overview]
Message-ID: <CAA93jw4mxx0fLS+yfZn=iJZNLhk5KTPZJ+AVZ_3XAhqo9bUhYg@mail.gmail.com> (raw)
In-Reply-To: <DB649488-4433-4FD6-A569-932BC08F444F@gmail.com>
On Sun, Apr 12, 2015 at 5:01 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> 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.
We need the simplicity of an rfc-compliant squash option in cake.
FQ is far more important than diffserv or aqm in sorting things
properly for most people. As noted elsewhere, what we see are packets
marked CS1 entering the system (treated as priority by most ethernet
devices) and then treated as background on wifi devices.
> 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.
I concur that remarking is too complex for cake. But squashing is not.
The ip header is hot in cache at the time at which it could occur,
also.
> 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
>
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
prev parent reply other threads:[~2015-04-13 15:30 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
2015-04-13 15:30 ` Dave Taht [this message]
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='CAA93jw4mxx0fLS+yfZn=iJZNLhk5KTPZJ+AVZ_3XAhqo9bUhYg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@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