From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-blk: Avoid zeroing every request structure
Date: Tue, 18 May 2010 11:29:17 -0500 [thread overview]
Message-ID: <4BF2C05D.70102@codemonkey.ws> (raw)
In-Reply-To: <4BF2BFA5.9000303@suse.de>
On 05/18/2010 11:26 AM, Alexander Graf wrote:
> Jes Sorensen wrote:
>
>> On 05/14/10 23:52, Stefan Hajnoczi wrote:
>>
>>
>>> The VirtIOBlockRequest structure is about 40 KB in size. This patch
>>> avoids zeroing every request by only initializing fields that are read.
>>> The other fields are either written to or may not be used at all.
>>>
>>> Oprofile shows about 10% of CPU samples in memset called by
>>> virtio_blk_alloc_request(). The workload is
>>> dd if=/dev/vda of=/dev/null iflag=direct bs=8k running concurrently 4
>>> times. This patch makes memset disappear to the bottom of the profile.
>>>
>>> Signed-off-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
>>>
>>>
>> Great catch!
>>
>> I ran some benchmarks using a ramdisk passed to the guest as a virtio
>> device and with this patch I saw improvements ranging from 5-20%. I
>> believe the fluctuations are due to not being able to numa bind it due
>> to limited memory.
>>
>> However a win all the way round!
>>
>>
> It looks like a fairly small change with a huge win. Sounds like a
> perfect candidate for 0.12.5 to me.
>
I'd prefer to stick to bug fixes for stable releases. Performance
improvements are a good motivation for people to upgrade to 0.13 :-)
Regards,
Anthony Liguori
> Alex
>
>
>
next prev parent reply other threads:[~2010-05-18 16:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 21:52 [Qemu-devel] [PATCH] virtio-blk: Avoid zeroing every request structure Stefan Hajnoczi
2010-05-16 13:25 ` Christoph Hellwig
2010-05-16 15:01 ` Stefan Hajnoczi
2010-05-18 9:36 ` Kevin Wolf
2010-05-18 15:46 ` Jes Sorensen
2010-05-18 16:26 ` Alexander Graf
2010-05-18 16:29 ` Anthony Liguori [this message]
2010-05-18 16:31 ` Alexander Graf
2010-05-29 13:07 ` Jamie Lokier
2010-05-18 16:37 ` Corentin Chary
2010-05-18 19:02 ` Stefan Hajnoczi
2010-05-18 19:55 ` Corentin Chary
2010-05-18 20:43 ` Stefan Hajnoczi
2010-05-21 11:17 ` Stefan Hajnoczi
2010-05-21 17:37 ` [Qemu-devel] [PATCH 0/2] Tidy qemu_malloc Richard Henderson
2010-05-28 22:08 ` Aurelien Jarno
2010-05-21 17:37 ` [Qemu-devel] [PATCH 1/2] Use calloc in qemu_mallocz Richard Henderson
2010-05-21 17:37 ` [Qemu-devel] [PATCH 2/2] linux-user: Use qemu-malloc.c Richard Henderson
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=4BF2C05D.70102@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Jes.Sorensen@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).