From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: Re: Mice [was Re: QoS for system critical packets on wireless]
Date: Wed, 22 Jun 2011 23:59:44 +0300 [thread overview]
Message-ID: <D613EB9A-9B1C-4169-94D9-1C2D0B733B7E@gmail.com> (raw)
In-Reply-To: <BANLkTi=aj4quHB3z3Je39BSwct-8Or15WA@mail.gmail.com>
On 22 Jun, 2011, at 11:11 pm, Dave Taht wrote:
> I further make a distinction between control packets and things like
> DNS/NTP and VOIP as per the above....
Tiny Information Transfers?
http://www.visordown.com/members/images/179524/gallery/ist2_2553987-great-tits.jpg
:-D
- Jonathan
next prev parent reply other threads:[~2011-06-22 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 19:39 Justin McCann
2011-06-22 20:11 ` Dave Taht
2011-06-22 20:42 ` Dave Taht
2011-06-22 20:59 ` Jonathan Morton [this message]
2011-06-22 21:06 ` Dave Taht
2011-06-23 2:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D613EB9A-9B1C-4169-94D9-1C2D0B733B7E@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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