From: Jens Axboe <axboe@kernel.dk>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "\"Xen-devel@lists.xensource.com\" li"
<Xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Daniel Stodden <daniel.stodden@citrix.com>
Subject: Re: [GIT PULL] xen blkfront barrier updates
Date: Fri, 12 Nov 2010 08:45:56 +0100 [thread overview]
Message-ID: <4CDCF0B4.9070508@kernel.dk> (raw)
In-Reply-To: <4CDC7A3C.8070206@goop.org>
On 2010-11-12 00:20, Jeremy Fitzhardinge wrote:
> Hi Jens,
>
> Here's the xen-blkfront barrier changes we discussed in Boston (its
> identical to the last posted version).
>
> The only comment was Christoph pointing out EOPNOTSUPP is not used in
> the block interface, but blkfront is just using it as a local
> placeholder and it never gets returned up to the block layer.
>
> I still haven't sorted out what's going on with the backends; we
> definitely need either a FLUSH operation or make empty WRITE_BARRIER
> work to flush disk caches.
Thanks Jeremy, I'll pull this in.
--
Jens Axboe
prev parent reply other threads:[~2010-11-12 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 23:20 [GIT PULL] xen blkfront barrier updates Jeremy Fitzhardinge
2010-11-12 7:45 ` Jens Axboe [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=4CDCF0B4.9070508@kernel.dk \
--to=axboe@kernel.dk \
--cc=Xen-devel@lists.xensource.com \
--cc=daniel.stodden@citrix.com \
--cc=hch@lst.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
/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