From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=54622 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pu4ke-0004Nd-4I for qemu-devel@nongnu.org; Mon, 28 Feb 2011 10:11:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pu4kb-0007J5-7x for qemu-devel@nongnu.org; Mon, 28 Feb 2011 10:11:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56024) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pu4ka-0007IR-Va for qemu-devel@nongnu.org; Mon, 28 Feb 2011 10:11:05 -0500 Message-ID: <4D6BBB72.6040205@redhat.com> Date: Mon, 28 Feb 2011 16:12:50 +0100 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC][PATCH 0/2] Allow cache settings for block devices to be changed at runtime. References: <20110228171956.05a84fb9@zephyr> In-Reply-To: <20110228171956.05a84fb9@zephyr> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Prerna Saxena Cc: Anthony Liguori , Ananth Narayan , Christoph Hellwig , qemu-devel , Stefan Hajnoczi 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. Christoph, what's the status of these patches? > 2. info block > Now extended to display cache settings for available block devices. Have you checked that libvirt is okay with this? Kevin