From: Dave Taht <dave.taht@gmail.com>
To: codel@lists.bufferbloat.net
Subject: [Codel] coping with memory limitations and packet flooding in codel and fq_codel
Date: Mon, 20 Aug 2012 14:05:42 -0700 [thread overview]
Message-ID: <CAA93jw7=K8Vvp6N5qYZ8gaODaFyZtAEjGyQe2BDh9-RBsvVHcQ@mail.gmail.com> (raw)
We've had a raft of deployment questions regarding fq_codel, memory
use, and the impact of unresponsive flows
over on the cerowrt development list.
sort of summary of the thread here, with some codel related ideas
https://lists.bufferbloat.net/pipermail/cerowrt-devel/2012-August/000423.html
some early data on wifi interactions here
https://lists.bufferbloat.net/pipermail/cerowrt-devel/2012-August/000407.html
--
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"
next reply other threads:[~2012-08-20 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 21:05 Dave Taht [this message]
2012-08-21 8:38 ` Eric Dumazet
2012-08-21 10:27 ` Andrew McGregor
2012-08-21 10:50 ` Eric Dumazet
2012-08-26 21:36 ` Dave Taht
2012-08-27 11:37 ` Eric Dumazet
2012-08-27 15:12 ` 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='CAA93jw7=K8Vvp6N5qYZ8gaODaFyZtAEjGyQe2BDh9-RBsvVHcQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=codel@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