From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qcow2: Improve cluster refcount update
Date: Fri, 07 Nov 2008 07:59:32 -0600 [thread overview]
Message-ID: <491449C4.4070500@codemonkey.ws> (raw)
In-Reply-To: <1226047453.4046.4.camel@frecb07144>
Laurent Vivier wrote:
> BTW, patch #1 is a clean-up (no change, only code move) and patch #2
> doesn't align buffer, but try to minimise syscall (it improves
> performance with O_DSYNC too).
>
> Ignore patch #3 and #4 if you dislike them.
>
But how useful is #1 and #2 if the buffers aren't aligned and we're
hitting the slow path?
Regards,
Anthony Liguori
> Regards,
> Laurent
>
next prev parent reply other threads:[~2008-11-07 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 16:55 [Qemu-devel] [PATCH 0/4] qcow2: Improve cluster refcount update Laurent Vivier
2008-11-06 18:53 ` Anthony Liguori
2008-11-07 8:31 ` Kevin Wolf
2008-11-07 8:44 ` Laurent Vivier
2008-11-07 13:59 ` Anthony Liguori [this message]
2008-11-07 15:01 ` Laurent Vivier
2008-11-07 15:37 ` Anthony Liguori
2008-11-07 15:48 ` Laurent Vivier
2008-11-09 14:35 ` Avi Kivity
2008-11-09 16:32 ` Anthony Liguori
2008-11-10 20:15 ` Andreas Färber
2008-11-10 20:52 ` Anthony Liguori
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=491449C4.4070500@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).