From: Dave Taht <dave.taht@bufferbloat.net>
To: netdev@vger.kernel.org, codel@lists.bufferbloat.net
Subject: [Codel] [PATCH 0/2] net-next codel enhancements
Date: Mon, 21 Oct 2013 18:19:55 -0700 [thread overview]
Message-ID: <1382404797-17239-1-git-send-email-dave.taht@bufferbloat.net> (raw)
These two patches have been extensively tested in openwrt
and cerowrt. Losing the fq_codel drop statistic as a bug.
Checking for a maxpacket size in the qdisc was somewhat
correct for ns2 but not for Linux as all the current
subsystems below htb/hfsc/adsl/bql buffer packets.
IMHO both of these patches are candidates for stable.
next reply other threads:[~2013-10-22 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 1:19 Dave Taht [this message]
2013-10-22 1:19 ` [Codel] [PATCH 1/2] fq_codel: keep dropped statistic around Dave Taht
2013-10-22 1:27 ` Eric Dumazet
2013-10-22 1:43 ` Dave Taht
2013-10-22 1:19 ` [Codel] [PATCH 2/2] codel: eliminate maxpacket as an inner bound 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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1382404797-17239-1-git-send-email-dave.taht@bufferbloat.net \
--to=dave.taht@bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=netdev@vger.kernel.org \
/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