qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] write barrier support
Date: Tue, 05 May 2009 16:53:25 +0300	[thread overview]
Message-ID: <4A0044D5.5010402@redhat.com> (raw)
In-Reply-To: <20090505120804.GA30651@lst.de>

Christoph Hellwig wrote:
> Add support for write barriers that allow guests to control write
> ordering when write back cachin is enabled.
>
> For now only the simple stack of virtio on posix raw/host devices is
> supported.
>   

I suggest emulating barriers for format drivers that don't support them 
by queuing the writes in the block layer and issuing a flush_all command.

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2009-05-05 13:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 12:08 [Qemu-devel] [PATCH 0/3] write barrier support Christoph Hellwig
2009-05-05 12:08 ` [Qemu-devel] barriers: block layer preparations Christoph Hellwig
2009-05-05 13:51   ` Avi Kivity
2009-05-05 15:38     ` Jamie Lokier
2009-05-05 15:49       ` Avi Kivity
2009-05-05 16:00         ` Jamie Lokier
2009-05-05 20:57     ` Christoph Hellwig
2009-05-05 22:49       ` Jamie Lokier
2009-05-05 12:08 ` [Qemu-devel] [PATCH 2/3] barriers: block-raw-posix barrier support Christoph Hellwig
2009-05-05 12:33   ` Jamie Lokier
2009-05-05 13:29     ` Christoph Hellwig
2009-05-05 16:00       ` Jamie Lokier
2009-05-05 12:09 ` [Qemu-devel] [PATCH 3/3] barriers: virtio Christoph Hellwig
2009-05-05 13:53 ` Avi Kivity [this message]
2009-05-05 21:00   ` [Qemu-devel] [PATCH 0/3] write barrier support Christoph Hellwig

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=4A0044D5.5010402@redhat.com \
    --to=avi@redhat.com \
    --cc=hch@lst.de \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).