From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] htb has internal pfifo queue
Date: Sun, 16 Jun 2013 14:32:14 -0700 [thread overview]
Message-ID: <CAA93jw6BNbH3DVxEMCjmK=BfAexRNONJ6rXLf-w950X0dMLuZg@mail.gmail.com> (raw)
In looking over the htb mess, I noticed that htb has an internal pfifo
queue, which is controllable via new stuff in net-next.
http://snapon.lab.bufferbloat.net/~cero2/htb_mess/11256-htb-add-HTB_DIRECT_QLEN-attribute.patch
I have no idea what, if anything, it affects. I was under the
impression, until now, that htb buffered up one, and only one packet
no matter how many classes you have. Still am retaining that
impression...
Ah well... fiddling with setting txqueuelen to 2 on the device on
3.8.13-7 before running the aqm script might have an interesting
result on simple.qos, if anyone wants to try it.
such a backlog of stuff to sort through!
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2013-06-16 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 21:32 Dave Taht [this message]
2013-06-17 3:54 ` Eric Dumazet
2013-06-17 16:38 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6BNbH3DVxEMCjmK=BfAexRNONJ6rXLf-w950X0dMLuZg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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