From: Christoph Hellwig <hch@lst.de>
To: ronniesahlberg@gmail.com
Cc: kwolf@redhat.com, hch@lst.de, qemu-devel@nongnu.org,
stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] iSCSI support for QEMU, update
Date: Fri, 22 Apr 2011 06:08:52 +0200 [thread overview]
Message-ID: <20110422040852.GA9493@lst.de> (raw)
In-Reply-To: <4db09239.0b968e0a.4145.ffffada2@mx.google.com>
On Fri, Apr 22, 2011 at 06:23:58AM +1000, ronniesahlberg@gmail.com wrote:
> iSCSI block driver for QEMU
>
> Please find an updated iSCSI patch.
> This patch adds setting FUA on all writes when the bit
> BDRV_O_CACHE_WB is not set.
At this point you need to check for BDRV_O_CACHE_WB and BDRV_O_NOCACHE
as they both have writeback cache semantics. I submitted a patch to clean
that up, but it didn't get merged yet.
next prev parent reply other threads:[~2011-04-22 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 20:23 [Qemu-devel] iSCSI support for QEMU, update ronniesahlberg
2011-04-22 4:08 ` Christoph Hellwig [this message]
2011-04-22 6:08 ` ronnie sahlberg
2011-04-22 6:13 ` Christoph Hellwig
2011-04-22 6:35 ` ronnie sahlberg
2011-04-22 6:38 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2011-05-07 6:17 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=20110422040852.GA9493@lst.de \
--to=hch@lst.de \
--cc=kwolf@redhat.com \
--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).