From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.jussieu.fr>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Notes about hacking on AQMs
Date: Thu, 23 Jun 2011 16:47:31 -0600 [thread overview]
Message-ID: <BANLkTi=nP5xq8EyZVB9+Q_MM=1vsH8Nwdw@mail.gmail.com> (raw)
In-Reply-To: <7ivcvwuqb1.fsf@lanthane.pps.jussieu.fr>
On Thu, Jun 23, 2011 at 4:38 PM, Juliusz Chroboczek <jch@pps.jussieu.fr> wrote:
>> I will also attempt to argue persuasively that having ECN packet marking in HTB
>
> I'm not following you. You can only perform ECN marking when you detect
> congestion; and you can only detect congestion if you're queueing.
> I may be wrong, but I believe that HTB doesn't do any queueing itself,
> it delegates queuing to its child qdiscs; hence, I don't see how you can
> perform ECN marking in HTB itself; you should be doing it in HTB's child
> qdisc.
You are right. I had spent a lot of time into HTB puzzling over how it
actually worked, observing lots of packet drops at it's level of stats
and nothing at the red level in the existing qos-scripts, and no
seeming correlation to the SFQ or hsfc either. It just didn't add up.
I'm still puzzling over it. But I grew to understand after posting
that mail that my issues were happening at the child qdiscs and I will
continue rewriting the rfc until it is both right AND clear.
Thx for catching up on the backlog.
>> RED has it's own idea as to the 'bandwidth' available, and does not
>> understand what it's getting has already been shaped by HTB.
>
> I'm not sure I understand that.
Neither do I and I'm going to go hide under a rock until I do.
> -- Juliusz
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next prev parent reply other threads:[~2011-06-23 22:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 12:12 Dave Taht
2011-06-08 12:56 ` Eric Dumazet
2011-06-08 13:32 ` Dave Taht
2011-06-08 14:04 ` Dave Taht
2011-06-08 14:57 ` Eric Dumazet
2011-06-08 15:20 ` Dave Taht
2011-06-08 15:21 ` Dave Taht
2011-06-23 22:38 ` Juliusz Chroboczek
2011-06-23 22:47 ` Dave Taht [this message]
2011-06-08 15:27 ` Jesper Dangaard Brouer
2011-06-08 15:45 ` Eric Dumazet
2011-06-08 15:51 ` Dave Taht
2011-06-08 16:41 ` Eric Dumazet
2011-06-08 16:52 ` Dave Taht
2011-06-08 17:50 ` Stephen Hemminger
2011-06-08 23:06 ` Thomas Graf
2011-06-09 17:18 ` Jesper Dangaard Brouer
2011-06-09 16:04 ` Jesper Dangaard Brouer
2011-06-09 16:14 ` Eric Dumazet
2011-06-09 17:20 ` Jesper Dangaard Brouer
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=nP5xq8EyZVB9+Q_MM=1vsH8Nwdw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.jussieu.fr \
/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