From: Kevin Wolf <kwolf@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block-raw: Make cache=off default again
Date: Mon, 22 Jun 2009 14:50:58 +0200 [thread overview]
Message-ID: <4A3F7E32.8090905@redhat.com> (raw)
In-Reply-To: <4A3F7B87.6000605@redhat.com>
Avi Kivity schrieb:
> On 06/22/2009 03:32 PM, Kevin Wolf wrote:
>>> Were your refcount-combining patches merged? I don't see them, and
>>> performance will suck without them.
>>>
>> They were merged some weeks ago, at least if a980c98c is what you mean.
>> I don't have any patches for inclusion that aren't merged yet (except
>> for this one, obviously).
>>
>
> I meant that, yes. Missed it going in.
>
> We still have a read-modify-write when extending an image, but I guess
> we're pretty close now, so it's worthwhile to try a guest install with
> cache=off.
As long as we don't have overlapping requests the RMW is basically a
memset, so at least on IDE this shouldn't hurt too much.
What happens with virtio I still need to understand. Obviously, as soon
as virtio decides to fall back to 4k requests, performance becomes
terrible. And if it doesn't, we still can get concurrent requests to the
same cluster, resulting in a real RMW (however, if it's only one RMW
remaining, it's kind of okay - last week's patches have removed some
more of them in the cluster allocation path...)
Kevin
next prev parent reply other threads:[~2009-06-22 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 11:18 [Qemu-devel] [PATCH] block-raw: Make cache=off default again Kevin Wolf
2009-06-22 11:35 ` Christoph Hellwig
2009-06-22 11:44 ` Kevin Wolf
2009-06-22 11:55 ` Avi Kivity
2009-06-22 12:32 ` Kevin Wolf
2009-06-22 12:39 ` Avi Kivity
2009-06-22 12:50 ` Kevin Wolf [this message]
2009-06-23 10:30 ` Jamie Lokier
2009-06-23 11:46 ` Kevin Wolf
2009-06-24 21:23 ` Jamie Lokier
2009-06-25 7:31 ` Kevin Wolf
2009-06-22 13:04 ` Christoph Hellwig
2009-06-22 13:05 ` Kevin Wolf
2009-06-22 13:14 ` Avi Kivity
2009-06-22 13:08 ` Anthony Liguori
2009-06-22 13:20 ` Kevin Wolf
2009-06-22 14:00 ` Anthony Liguori
2009-06-22 13:23 ` Dor Laor
2009-06-22 13:29 ` Kevin Wolf
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=4A3F7E32.8090905@redhat.com \
--to=kwolf@redhat.com \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.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).