From: Tristan Seligmann <mithrandi@mithrandi.net>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Bufferbloat overview article
Date: Sun, 3 Mar 2013 01:31:51 +0200 [thread overview]
Message-ID: <CAMcKhMSDz0BZGSWBMU9anVZ0hZBhooAzLP0nS3C+wVEUF1kftA@mail.gmail.com> (raw)
As part of my adventures into (de)bloating my home router (which is an
x86 box running Debian, rather than openwrt/cerowrt or similar), I've
always intended to document the details on my blog once I got a
chance. I recently started work on this; since the first post I wrote
is just a general exploration of the "bufferbloat" problem, and it's
been well-received by everyone I've shown it to so far, I thought I'd
pass it around:
https://mithrandi.net/blog/2013/02/a-brief-history-of-bufferbloat/
Comments & criticism welcome; either in the comments, or by email.
The follow-up posts I have planned will dig more deeply into the
details of kernel patching, tuning fq_codel, htb ratelimits, and so
on. I'll probably also take a crack at packaging some of the tools
(such as netperf-wrapper) that aren't currently available as Debian
packages.
--
mithrandi, i Ainil en-Balandor, a faer Ambar
next reply other threads:[~2013-03-02 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 23:31 Tristan Seligmann [this message]
2013-03-03 13:26 ` Toke Høiland-Jørgensen
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=CAMcKhMSDz0BZGSWBMU9anVZ0hZBhooAzLP0nS3C+wVEUF1kftA@mail.gmail.com \
--to=mithrandi@mithrandi.net \
--cc=bloat@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