From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: "nbd-general@lists.sourceforge.net"
<nbd-general@lists.sourceforge.net>, Wouter Verhelst <w@uter.be>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCHv3] Improve the documentation of NBD_CMD_FLUSH and NBD_CMD_FLAG_FUA.
Date: Tue, 5 Apr 2016 17:22:39 +0200 [thread overview]
Message-ID: <5703D83F.60708@redhat.com> (raw)
In-Reply-To: <9A3BB330-4BFC-48AA-A129-89CB521A35FC@alex.org.uk>
On 05/04/2016 17:16, Alex Bligh wrote:
> > > * Document that sending FUA for commands that do nothing is permissible, but
> > > 'SHOULD NOT' be done; an existing client does this.
> >
> > Can you send a pointer to the discussion? FUA on reads definitely does
> > *something* in SCSI (it ensures that the data is moved out of the
> > volatile cache prior to the read, similar to what QEMU implements).
>
> Sure. I got a solitary one reply that referenced the kernel, which
> was copied to this list - see below.
Ok, thanks.
> I don't have strong feelings either way, but the safer option would
> be to not REQUIRE the server to rely on any FUA read behaviour (I'm
> already saying they should ignore the bit on reads). Qemu can't
> currently RELY on FUA on reads, as it's not documented anywhere
> and with the reference NBD server did nothing until recently; recently
> it started errorring the read! See below.
Right. However, bugs get fixed...
Paolo
> On that basis I chose to go with 'FUA on read does nothing'.
>
> If the kernel actually does something on read perhaps we should
> reconsider.
next prev parent reply other threads:[~2016-04-05 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 12:07 [Qemu-devel] [PATCHv3] Improve the documentation of NBD_CMD_FLUSH and NBD_CMD_FLAG_FUA Alex Bligh
2016-04-05 14:22 ` Eric Blake
2016-04-05 15:11 ` Alex Bligh
2016-04-05 14:30 ` Paolo Bonzini
2016-04-05 15:16 ` Alex Bligh
2016-04-05 15:22 ` Paolo Bonzini [this message]
2016-04-05 15:25 ` Alex Bligh
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=5703D83F.60708@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex@alex.org.uk \
--cc=nbd-general@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=w@uter.be \
/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.