From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] what to do about xen?
Date: Wed, 15 Apr 2015 22:08:39 -0700 [thread overview]
Message-ID: <1429160919.7346.165.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAA93jw4J_VupkHY0CtGi4bTp3zHCVaLHn3fe7V3FayM-xaXK3Q@mail.gmail.com>
Hmpff.
Apparently, the mechanisms we put in place are black magic for most
people.
Burn the magicians, so that good people can live in peace.
On Wed, 2015-04-15 at 20:15 -0700, Dave Taht wrote:
> see thread at: https://lkml.org/lkml/2015/4/15/448
>
prev parent reply other threads:[~2015-04-16 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 3:15 Dave Taht
2015-04-16 5:08 ` Eric Dumazet [this message]
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=1429160919.7346.165.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@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