From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46755) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tsua7-0006Qs-Mp for qemu-devel@nongnu.org; Wed, 09 Jan 2013 07:16:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tsua6-00085v-Nb for qemu-devel@nongnu.org; Wed, 09 Jan 2013 07:16:31 -0500 Received: from mail-pa0-f43.google.com ([209.85.220.43]:43540) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tsua6-00085q-H1 for qemu-devel@nongnu.org; Wed, 09 Jan 2013 07:16:30 -0500 Received: by mail-pa0-f43.google.com with SMTP id fb10so1003712pad.30 for ; Wed, 09 Jan 2013 04:16:29 -0800 (PST) Message-ID: <50ED5F95.2060403@gmail.com> Date: Wed, 09 Jan 2013 20:16:21 +0800 From: Liu Yuan MIME-Version: 1.0 References: <1355941771-3418-1-git-send-email-namei.unix@gmail.com> <87k3s6shdv.wl%morita.kazutaka@lab.ntt.co.jp> <50D967C3.7020109@gmail.com> <50E58B19.2050701@gmail.com> <20130104163830.GF6310@stefanha-thinkpad.hitronhub.home> <50E7AEC4.5080309@gmail.com> <50E7BA41.3020307@gmail.com> <50E7DC9B.4080309@gmail.com> <50EACC61.2020603@redhat.com> <50EBB1CB.9030608@gmail.com> <20130108094025.GE2557@stefanha-thinkpad.redhat.com> <50EBEAD2.6070608@gmail.com> <50EBEE42.7010407@redhat.com> <50EBF755.3050607@gmail.com> <50EBFA3F.8030808@redhat.com> <50EBFE20.9010100@gmail.com> <50EC00CE.80205@redhat.com> <50EC0493.8030701@gmail.com> <50EC0D41.4070200@redhat.com> <50EC1C9A.5040006@gmail.com> <50ED45A8.5020706@redhat.com> <50ED4829.1070302@gmail.com> <50ED4933.3040001@redhat.com> <50ED4A90.2080808@gmail.com> <50ED5D64.4040600@gmail.com> In-Reply-To: <50ED5D64.4040600@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] sheepdog: implement direct write semantics List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Kevin Wolf , Stefan Hajnoczi , qemu-devel@nongnu.org, MORITA Kazutaka On 01/09/2013 08:07 PM, Liu Yuan wrote: > and my proposal (adding another field to BlockDriverState to allow > self-interpretation cache flag) can work well with current block layer: > > Sheepdog driver behavior: > cache flags WCE toggled and resulting behavior > writethrough writethrough > writeback writetrhough (writeback + flush) > > We can see that the writeback behavior for Guest-WCE toggling is the > same as expected. The difference is that if we set cache=writethrough, > guest can't change it via WCE toggling. I am wondering if above scheme can apply to the block layer, then 'cache=xxx' can act as a stronger control over WCE toggling. Then we don't need extra field. Thanks, Yuan