From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Three new diffserv codepoints suggested
Date: Mon, 13 Jun 2011 17:10:42 +0300 [thread overview]
Message-ID: <7A482BB8-D269-4B93-A3B0-24E0C6773055@gmail.com> (raw)
In-Reply-To: <BANLkTikk8Tdj6+NSQ69hfMPOO33MPUrKkA@mail.gmail.com>
I thought: Most Important Control Engrams.
Also, Linux 3.0 appears to be getting QFQ which might be a better alternative to SFQ. I've read the paper and it seems to be both clever and sufficiently simple to work.
The key to knowledge is not to rely on others to teach you it.
On 11 Jun 2011, at 16:15, Dave Taht <dave.taht@gmail.com> wrote:
> I was unable to come up with a back-acronym for 'mice'. I got as
> far as 'majorly important' before getting stuck on the 'c'.
next prev parent reply other threads:[~2011-06-13 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 13:15 Dave Taht
2011-06-12 5:05 ` Dave Taht
2011-06-13 14:10 ` Jonathan Morton [this message]
2011-06-13 14:35 ` 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/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=7A482BB8-D269-4B93-A3B0-24E0C6773055@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@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