From: Stefan Hajnoczi <stefanha@gmail.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
stefanha@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] iSCSI support for QEMU
Date: Thu, 21 Apr 2011 13:08:27 +0100 [thread overview]
Message-ID: <BANLkTinnuwxhAZGDgAtgD7=6hcPPuXsUGA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikpghHCNFr5NbYLoUw+Z55rDvH+Sg@mail.gmail.com>
On Thu, Apr 21, 2011 at 12:36 PM, ronnie sahlberg
<ronniesahlberg@gmail.com> wrote:
> I understand.
>
> Let me re-send a patch tomorrow that can optionally enable/force FUA
> bits for write.
> There are some high-volume arrays that advertise support but fail any
> cdb with FUA, FUA_NV bits set with sense, so it needs to be made optional.
Maybe we should just disable write cache on the LUN (setting WCE=0) if
cache=writethrough? Then we don't need to worry about FUA or
synchronize cache.
Stefan
next prev parent reply other threads:[~2011-04-21 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 8:43 [Qemu-devel] iSCSI support for QEMU Ronnie Sahlberg
2011-04-21 8:43 ` [Qemu-devel] [PATCH] iSCSI block driver support Ronnie Sahlberg
2011-04-21 8:50 ` [Qemu-devel] iSCSI support for QEMU Christoph Hellwig
2011-04-21 8:58 ` ronnie sahlberg
2011-04-21 9:09 ` Christoph Hellwig
2011-04-21 9:28 ` ronnie sahlberg
2011-04-21 10:58 ` Stefan Hajnoczi
2011-04-21 11:12 ` ronnie sahlberg
2011-04-21 11:21 ` Stefan Hajnoczi
2011-04-21 11:36 ` ronnie sahlberg
2011-04-21 11:44 ` Kevin Wolf
2011-04-21 12:08 ` Stefan Hajnoczi [this message]
2011-04-21 12:49 ` Christoph Hellwig
2011-04-21 20:25 ` ronnie sahlberg
2011-04-21 9:47 ` ronnie sahlberg
-- strict thread matches above, loose matches on Subject: below --
2011-06-12 2:54 ronnie sahlberg
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='BANLkTinnuwxhAZGDgAtgD7=6hcPPuXsUGA@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@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 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).