From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"famz@redhat.com" <famz@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Orit Wasserman <owasserm@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv2] block: add native support for NFS
Date: Thu, 19 Dec 2013 15:31:53 +0100 [thread overview]
Message-ID: <52B30359.6040901@redhat.com> (raw)
In-Reply-To: <0610458E-282F-4ABC-96CA-498E4661485E@kamp.de>
Il 18/12/2013 18:21, Peter Lieven ha scritto:
> Not completely I think, but please correct me if I am wrong.
>
> If cache=writeback is set we issue just a write. In libnfs or libiscsi case
> that guarantees that the request has been successfully executed
> on the target / server. This is enough to be consistent in case of
> migration because consecutive reads will be answered correctly.
>
> But the target / server is still free to just keep this
> data in memory so we should only set this if we know that the target / server
> e.g. has a battery backup or we know that the filesystem uses e.g. barriers and
> issues a flush at important points.
Yes. However, the same holds for cache=none (both on
libnfs/libiscsi/NBD/others, where it is a nop, and on regular I/O, where
it uses O_DIRECT *but not O_SYNC or O_DSYNC*).
> If cache=none is set we issue a flush after every single write.
That's what you get with cache=writethrough or cache=directsync. Here
the flush is added automatically by the block layer, so it works with
every driver.
Paolo
next prev parent reply other threads:[~2013-12-19 14:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 9:15 [Qemu-devel] [PATCHv2] block: add native support for NFS Peter Lieven
2013-12-17 16:47 ` Stefan Hajnoczi
2013-12-17 17:03 ` Peter Lieven
2013-12-17 17:13 ` ronnie sahlberg
2013-12-17 22:36 ` Peter Lieven
2013-12-17 22:44 ` Eric Blake
2013-12-17 22:51 ` ronnie sahlberg
2013-12-17 22:56 ` Peter Lieven
2013-12-17 17:28 ` ronnie sahlberg
2013-12-17 23:00 ` Peter Lieven
2013-12-20 9:48 ` Peter Lieven
2013-12-20 12:19 ` Stefan Hajnoczi
2013-12-20 12:53 ` Peter Lieven
2013-12-20 13:57 ` Stefan Hajnoczi
2013-12-20 14:07 ` Peter Lieven
2013-12-20 14:38 ` Stefan Hajnoczi
2013-12-20 14:43 ` Peter Lieven
2013-12-20 15:03 ` ronnie sahlberg
2013-12-20 15:30 ` Stefan Hajnoczi
2013-12-20 15:49 ` Peter Lieven
2013-12-20 15:54 ` Stefan Hajnoczi
2013-12-20 15:57 ` Peter Lieven
2013-12-20 16:27 ` Stefan Hajnoczi
2014-01-03 10:35 ` Peter Lieven
2013-12-17 16:53 ` ronnie sahlberg
2013-12-17 22:57 ` Peter Lieven
2013-12-17 17:32 ` Daniel P. Berrange
2013-12-17 23:03 ` Peter Lieven
2013-12-18 9:30 ` Daniel P. Berrange
2013-12-18 10:00 ` Orit Wasserman
2013-12-18 10:18 ` Daniel P. Berrange
2013-12-18 10:24 ` Orit Wasserman
2013-12-18 10:38 ` Paolo Bonzini
2013-12-18 17:21 ` Peter Lieven
2013-12-19 14:31 ` Paolo Bonzini [this message]
2013-12-18 11:11 ` Peter Lieven
2013-12-18 11:23 ` Orit Wasserman
2013-12-18 14:42 ` ronnie sahlberg
2013-12-18 16:59 ` Peter Lieven
2013-12-18 17:33 ` ronnie sahlberg
2013-12-18 17:42 ` Peter Lieven
2013-12-18 17:50 ` ronnie sahlberg
2013-12-18 17:55 ` Peter Lieven
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=52B30359.6040901@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=owasserm@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.