qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Ananth Narayan <ananth@linux.vnet.ibm.com>,
	Prerna Saxena <prerna@linux.vnet.ibm.com>,
	Chunqiang Tang <ctang@us.ibm.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [RFC][PATCH 0/2] Allow cache settings for block devices to be changed at runtime.
Date: Tue, 1 Mar 2011 09:55:05 +0000	[thread overview]
Message-ID: <AANLkTimU4QSXvq-kTY63ynqvtyDDdSNnTs1RF=kPfEDJ@mail.gmail.com> (raw)
In-Reply-To: <4D6BC3DE.7000208@redhat.com>

On Mon, Feb 28, 2011 at 3:48 PM, Kevin Wolf <kwolf@redhat.com> wrote:
> Am 28.02.2011 16:35, schrieb Stefan Hajnoczi:
>> On Mon, Feb 28, 2011 at 3:12 PM, Kevin Wolf <kwolf@redhat.com> wrote:
>>> Am 28.02.2011 12:49, schrieb Prerna Saxena:
>>>> The following patchset introduces monitor commands:
>>>>
>>>> 1. set_cache DEVICE CACHE-SETTING
>>>> Change cache settings for block device, DEVICE, through the monitor.
>>>> (Available options : 'none', 'writeback', 'writethrough')
>>>> Eg,
>>>> (qemu)set_cache ide0-hd0 none
>>>> -> Changes cache setting for ide0-hd0 to 'none'
>>>
>>> Not sure if adding this interface is a good idea. I see that you only
>>> add it for HMP, and we may consider that, but it's definitely not
>>> suitable for QMP.
>>>
>>> One reason is that none/writethrough/writeback/unsafe isn't really what
>>> we want to use long term. We want to separate advertising a write cache
>>> (which is guest visible) from things like whether to use O_DIRECT or not.
>>>
>>> In the past, Christoph mentioned that he had patches to make these
>>> separate and even let the guest change the "write cache enabled" flag,
>>> which would probably solve most of the use cases of this patch.
>>
>> Toggling host page cache at runtime is useful too because it saves
>> having to restart VMs.
>
> Not sure why I wanted to change that during runtime, but agreed,
> allowing to change parameters using the monitor is generally a good thing.
>
> However, I'm not sure if a command for changing the cache mode is the
> right solution, or if it should be something like a command to change
> block device options. (For example, what about toggling read-only or
> snapshot mode?)

Yes, I think you're right.  We should aim for a general interface
rather than having to add many more specific interfaces in the future.

CQ: Do you see a relation to the "update" interface you added to
adjust drive options at runtime for FVD?

Stefan

  reply	other threads:[~2011-03-01  9:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 11:49 [Qemu-devel] [RFC][PATCH 0/2] Allow cache settings for block devices to be changed at runtime Prerna Saxena
2011-02-28 12:07 ` [Qemu-devel] [RFC][PATCH 1/2] Add monitor command 'set-cache' to change cache settings for a block device Prerna Saxena
2011-02-28 12:11 ` [Qemu-devel] [RFC][PATCH 2/2] Extend monitor command 'info block' to display cache settings for block devices Prerna Saxena
2011-02-28 15:15   ` Kevin Wolf
2011-02-28 15:12 ` [Qemu-devel] [RFC][PATCH 0/2] Allow cache settings for block devices to be changed at runtime Kevin Wolf
2011-02-28 15:35   ` Stefan Hajnoczi
2011-02-28 15:48     ` Kevin Wolf
2011-03-01  9:55       ` Stefan Hajnoczi [this message]
2011-03-01 10:06         ` Kevin Wolf
2011-03-01 15:02           ` Chunqiang Tang
2011-03-01 13:03       ` Anthony Liguori
2011-03-01 13:22         ` Kevin Wolf
2011-03-01 15:47           ` Anthony Liguori
2011-03-01 12:42     ` Christoph Hellwig
2011-03-01 12:48       ` Stefan Hajnoczi
2011-03-01 12:50         ` Christoph Hellwig
2011-03-01 19:13           ` Anthony Liguori
2011-03-02  7:57             ` Kevin Wolf
2011-03-01 12:52       ` 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='AANLkTimU4QSXvq-kTY63ynqvtyDDdSNnTs1RF=kPfEDJ@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=ctang@us.ibm.com \
    --cc=hch@lst.de \
    --cc=kwolf@redhat.com \
    --cc=prerna@linux.vnet.ibm.com \
    --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).