qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liu Yuan <namei.unix@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org,
	MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] sheepdog: implement direct write semantics
Date: Tue, 08 Jan 2013 13:42:35 +0800	[thread overview]
Message-ID: <50EBB1CB.9030608@gmail.com> (raw)
In-Reply-To: <50EACC61.2020603@redhat.com>

On 01/07/2013 09:23 PM, Kevin Wolf wrote:
> No, and in theory they shouldn't have to care.
> 
> Why do you want to handle writethrough semantics in the block driver
> rather than letting qemu care for sending the right flushes?

Because Sheepdog itself provide the client side cache implementation and
we need means to get the cache hint from users when starting up the VM.
This cache support:
 writethrough: provide a read cache for this VM, which is always
consistent with cluster data
 writeback: provide a writeback cache for this VM, which only flush the
dirty bits when VM send 'flush' request.
 directio: disable cache completely for this VM.

Old QEMU (before v1.2) allows block drivers to get the cache flags, so
Sheepdog can interpret these flags on its own to choose the right cache
mode for each VM. doesn't QEMU need keep backward compatibility?

Thanks,
Yuan

  reply	other threads:[~2013-01-08  5:42 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 18:29 [Qemu-devel] [PATCH] sheepdog: implement direct write semantics Liu Yuan
2012-12-25  7:47 ` MORITA Kazutaka
2012-12-25  8:26   ` Liu Yuan
2012-12-25  8:45   ` Liu Yuan
2013-01-03 13:43     ` Liu Yuan
2013-01-04 16:38       ` Stefan Hajnoczi
2013-01-05  4:40         ` Liu Yuan
2013-01-05  5:29           ` Liu Yuan
2013-01-05  7:56             ` Liu Yuan
2013-01-07 12:31               ` Stefan Hajnoczi
2013-01-08  5:28                 ` Liu Yuan
2013-01-07 13:23               ` Kevin Wolf
2013-01-08  5:42                 ` Liu Yuan [this message]
2013-01-08  9:40                   ` Stefan Hajnoczi
2013-01-08  9:45                     ` Liu Yuan
2013-01-08 10:00                       ` Kevin Wolf
2013-01-08 10:39                         ` Liu Yuan
2013-01-08 10:51                           ` Kevin Wolf
2013-01-08 11:08                             ` Liu Yuan
2013-01-08 11:19                               ` Kevin Wolf
2013-01-08 11:35                                 ` Liu Yuan
2013-01-08 12:12                                   ` Kevin Wolf
2013-01-08 13:18                                     ` Liu Yuan
2013-01-08 13:23                                       ` Liu Yuan
2013-01-09 10:25                                       ` Paolo Bonzini
2013-01-09 10:36                                         ` Liu Yuan
2013-01-09 10:40                                           ` Paolo Bonzini
2013-01-09 10:46                                             ` Liu Yuan
2013-01-09 10:58                                               ` Liu Yuan
2013-01-09 11:10                                                 ` Paolo Bonzini
2013-01-09 12:07                                               ` Liu Yuan
2013-01-09 12:10                                                 ` Liu Yuan
2013-01-09 12:16                                                 ` Liu Yuan
2013-01-09 12:42                                                 ` Kevin Wolf
2013-01-09 13:04                                                   ` Liu Yuan
2013-01-09 15:10                                                     ` Paolo Bonzini
2013-01-10  5:38                                                       ` Liu Yuan
2013-01-11  7:52                                                         ` MORITA Kazutaka
2013-01-11  8:07                                                           ` Liu Yuan
2013-01-11  9:00                                                             ` Paolo Bonzini
2013-01-11  9:04                                                               ` Liu Yuan
2013-01-11  9:34                                                                 ` Paolo Bonzini
2013-01-11  9:38                                                                   ` Liu Yuan
2013-01-11  9:40                                                                     ` Paolo Bonzini
2013-01-11  9:32                                                           ` Kevin Wolf
2013-01-10 15:25                                                       ` Jamie Lokier
2013-01-10 15:31                                                         ` Paolo Bonzini
2013-01-10 17:22                                                           ` Jamie Lokier
2013-01-09 11:10                                           ` Kevin Wolf
2013-01-09 10:23                                     ` Paolo Bonzini
2013-01-10 15:12                             ` Jamie Lokier
2013-01-10 15:21                               ` Kevin Wolf
2013-01-10  8:03 ` [Qemu-devel] [PATCH v2] " Liu Yuan
2013-01-10  9:04   ` Stefan Hajnoczi
2013-01-11  7:35   ` MORITA Kazutaka
2013-01-11  9:23     ` 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=50EBB1CB.9030608@gmail.com \
    --to=namei.unix@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).