From: Dan Siemon <dan@coverfire.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Queueing in the Linux Network Stack
Date: Wed, 07 Aug 2013 21:01:23 -0400 [thread overview]
Message-ID: <1375923683.2236.6.camel@ganymede.home> (raw)
My article on Queueing in the Linux Network Stack was in the July 2013
issue of Linux Journal. It's now available online at my site and may be
interesting to the Bufferbloat audience.
http://www.coverfire.com/articles/queueing-in-the-linux-network-stack/
reply other threads:[~2013-08-08 1:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1375923683.2236.6.camel@ganymede.home \
--to=dan@coverfire.com \
--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