From: Kevin Wolf <kwolf@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Federico Simoncelli <fsimonce@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] qemu-img: Add nocache command line option
Date: Wed, 15 Jun 2011 12:50:21 +0200 [thread overview]
Message-ID: <4DF88E6D.2000304@redhat.com> (raw)
In-Reply-To: <4DF75E61.2010500@redhat.com>
Am 14.06.2011 15:13, schrieb Avi Kivity:
> On 06/14/2011 03:09 PM, Federico Simoncelli wrote:
>> qemu-img currently writes images using writeback and filling up
>> the cache buffers which are then flushed by the kernel preventing
>> other processes from accessing the storage.
>> This is particularly bad in cluster environments where time-based
>> algorithms might be in place and accessing the storage within
>> certain timeouts is critical.
>> This patch adds the option to use nocache when other solutions
>> (eg: cgroups) are not available.
Your patch confuses a write-through cache (cache=writethrough == O_SYNC)
with bypassing the cache (cache=none == O_DIRECT), which are entirely
different.
> Please copy qemu-devel@nongnu.org as this is not a kvm-specific patch.
>
>> diff --git a/qemu-img.c b/qemu-img.c
>> index 4f162d1..c10e4a6 100644
>> --- a/qemu-img.c
>> +++ b/qemu-img.c
>> @@ -78,6 +78,7 @@ static void help(void)
>> " rebasing in this case (useful for renaming the backing file)\n"
>> " '-h' with or without a command shows this help and lists the supported formats\n"
>> " '-p' show progress of command (only certain commands)\n"
>> + " '-t' use write-through (no cache), valid with: convert, commit and rebase\n"
>> "\n"
>> "Parameters to snapshot subcommand:\n"
>> " 'snapshot' is the name of the snapshot to create, apply or delete\n"
>
> IMO better to use the existing qemu option format, say -o
> cache=writeback|writethrough|none|volatile.
No, -o is used with qemu-img create for options that change what the
image will look like (e.g. setting flags in the image header). This
options is about the cache mode that is used for various operations.
Kevin
next prev parent reply other threads:[~2011-06-15 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 12:09 [PATCH] qemu-img: Add nocache command line option Federico Simoncelli
2011-06-14 13:13 ` Avi Kivity
2011-06-15 10:50 ` Kevin Wolf [this message]
2011-06-15 11:17 ` Federico Simoncelli
2011-06-15 11:45 ` Kevin Wolf
2011-06-15 12:15 ` Federico Simoncelli
2011-06-15 12:26 ` Kevin Wolf
2011-06-15 13:46 ` [PATCH] qemu-img: Add cache " Federico Simoncelli
2011-06-15 13:51 ` [PATCHv2] " Federico Simoncelli
2011-06-16 11:58 ` [PATCHv3] " Federico Simoncelli
2011-06-16 14:28 ` [Qemu-devel] [PATCH] " Christoph Hellwig
2011-06-16 14:43 ` Kevin Wolf
2011-06-20 14:47 ` Kevin Wolf
2011-06-20 16:48 ` [PATCHv4] " Federico Simoncelli
2011-06-29 9:48 ` Kevin Wolf
2011-06-16 14:44 ` [Qemu-devel] [PATCH] " Federico Simoncelli
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=4DF88E6D.2000304@redhat.com \
--to=kwolf@redhat.com \
--cc=avi@redhat.com \
--cc=fsimonce@redhat.com \
--cc=kvm@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