From: "Michael S. Tsirkin" <mst@redhat.com>
To: Shirley Ma <mashirle@us.ibm.com>
Cc: Mike Waychison <mikew@google.com>,
Rusty Russell <rusty@rustcorp.com.au>,
kvm@vger.kernel.org, virtualization@lists.osdl.org,
netdev@vger.kernel.org
Subject: Re: [PATCH RFC net-next] virtio_net: refill buffer right after being used
Date: Wed, 3 Aug 2011 23:30:20 +0300 [thread overview]
Message-ID: <20110803203020.GB19501@redhat.com> (raw)
In-Reply-To: <1312089375.23194.11.camel@localhost.localdomain>
On Sat, Jul 30, 2011 at 10:16:15PM -0700, Shirley Ma wrote:
> It averages the latency between each receive by filling only one set of
> buffers vs. either none buffers or 1/2 ring size buffers fill between
> receives.
I see how the overhead of allocating memory is spread more evenly. Does this
actually help some workloads?
next prev parent reply other threads:[~2011-08-03 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 22:44 [PATCH RFC net-next] virtio_net: refill buffer right after being used Shirley Ma
2011-07-29 22:55 ` Shirley Ma
2011-07-29 23:58 ` Mike Waychison
2011-07-31 5:16 ` Shirley Ma
2011-08-03 20:30 ` Michael S. Tsirkin [this message]
2011-08-03 20:26 ` Michael S. Tsirkin
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=20110803203020.GB19501@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=mikew@google.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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).