All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Re: [PATCH v3 5/5] qed: Consistency check support
Date: Thu, 28 Oct 2010 13:02:58 +0200	[thread overview]
Message-ID: <4CC95862.8090908@redhat.com> (raw)
In-Reply-To: <AANLkTimeYNiE25zpSmgMkNHKVA0oZ0GgmG27EQ=JCqXz@mail.gmail.com>

  On 10/28/2010 12:51 PM, Stefan Hajnoczi wrote:
> >
> >  Opening the file read-only first and reopening it read-write when the
> >  migration has completed would be much better. No image format driver
> >  would have to be changed for that.
>
> I agree.  I'm not sure whether NFS guarantees we see the latest data
> when reopening read-write (cached pages will be left on the
> destination host from the initial read-only access).
>

AFAICT the re-open has to re-validate the metadata.  If ctime has 
changed since the previous stat, the client has to drop local caches.

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

      reply	other threads:[~2010-10-28 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 14:56 [Qemu-devel] (no subject) Stefan Hajnoczi
2010-10-22 14:56 ` [Qemu-devel] [PATCH v3 1/5] docs: Add QED image format specification Stefan Hajnoczi
2010-10-22 14:56 ` [Qemu-devel] [PATCH v3 2/5] qed: Add QEMU Enhanced Disk image format Stefan Hajnoczi
2010-10-22 14:56 ` [Qemu-devel] [PATCH v3 3/5] qed: Table, L2 cache, and cluster functions Stefan Hajnoczi
2010-10-22 14:56 ` [Qemu-devel] [PATCH v3 4/5] qed: Read/write support Stefan Hajnoczi
2010-10-22 14:56 ` [Qemu-devel] [PATCH v3 5/5] qed: Consistency check support Stefan Hajnoczi
2010-10-27 15:52   ` [Qemu-devel] " Kevin Wolf
2010-10-28 10:15     ` Stefan Hajnoczi
2010-10-28 10:37       ` Kevin Wolf
2010-10-28 10:51         ` Stefan Hajnoczi
2010-10-28 11:02           ` Avi Kivity [this message]

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=4CC95862.8090908@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=hch@lst.de \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.