From: Stefan Hajnoczi <stefanha@gmail.com>
To: Shirley Ma <mashirle@us.ibm.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] vhost: Reduce TX used buffer signal for performance
Date: Thu, 28 Oct 2010 09:59:39 +0100 [thread overview]
Message-ID: <AANLkTikgiFFCTK7aBChwt0vj3BGJpM2zO44-nDDQeHaM@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinqG_G2pevoYJyiHiBda1ZZS-53Uqz9WEspbMOy@mail.gmail.com>
On Thu, Oct 28, 2010 at 9:57 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
Just read the patch 1/1 discussion and it looks like you're already on
it. Sorry for the noise.
Stefan
prev parent reply other threads:[~2010-10-28 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 21:00 [RFC PATCH 0/1] vhost: Reduce TX used buffer signal for performance Shirley Ma
2010-10-27 21:05 ` Shirley Ma
2010-10-28 8:57 ` Stefan Hajnoczi
2010-10-28 8:59 ` Stefan Hajnoczi [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikgiFFCTK7aBChwt0vj3BGJpM2zO44-nDDQeHaM@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).