From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
"Theodore Ts'o" <tytso@mit.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: linux-next regression: IO errors in with ext4 and xen-blkfront
Date: Fri, 22 Oct 2010 05:20:15 -0400 [thread overview]
Message-ID: <20101022092015.GA18290@infradead.org> (raw)
In-Reply-To: <4CC15204.90206@kernel.dk>
On Fri, Oct 22, 2010 at 10:57:40AM +0200, Jens Axboe wrote:
> On 2010-10-22 10:56, Christoph Hellwig wrote:
> > On Fri, Oct 22, 2010 at 10:54:54AM +0200, Jens Axboe wrote:
> >> So how about we just disable barriers for Xen atm? I would really really
> >> like to push that branch out as well now, since I'll be travelling for
> >> most of the merge window this time.
> >
> > Yes, that's what removing/commenting out that line does.
>
> Certainly, but I meant in the barrier branch for submission. If
> it doesn't do empty flushes to begin with, that should be fixed
> up before being enabled in any case.
Yes, it should have been disabled log ago. I had a long discussion with
them abnout it when they introduced the even more buggy barriers by
tags mode for .36 but they simply ignored it.
> I'll disable barrier support in xen-blkfront.c for now.
Thanks.
next prev parent reply other threads:[~2010-10-22 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 0:04 linux-next regression: IO errors in with ext4 and xen-blkfront Jeremy Fitzhardinge
2010-10-21 0:09 ` Jeremy Fitzhardinge
2010-10-22 8:18 ` Jens Axboe
2010-10-22 8:29 ` Christoph Hellwig
2010-10-22 8:54 ` Jens Axboe
2010-10-22 8:56 ` Christoph Hellwig
2010-10-22 8:57 ` Jens Axboe
2010-10-22 9:20 ` Christoph Hellwig [this message]
2010-10-25 18:26 ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-10-25 18:47 ` Christoph Hellwig
2010-10-25 19:05 ` Konrad Rzeszutek Wilk
2010-10-26 12:49 ` Daniel Stodden
2010-10-27 10:23 ` Christoph Hellwig
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=20101022092015.GA18290@infradead.org \
--to=hch@infradead.org \
--cc=Xen-devel@lists.xensource.com \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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