From: Alasdair G Kergon <agk@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Andi Kleen <andi@firstfloor.org>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Milan Broz <mbroz@redhat.com>
Subject: Re: [PATCH] Implement barrier support for single device DM devices
Date: Tue, 19 Feb 2008 02:39:00 +0000 [thread overview]
Message-ID: <20080219023900.GB4066@agk.fab.redhat.com> (raw)
In-Reply-To: <47B58EAA.8040405@msgid.tls.msk.ru>
On Fri, Feb 15, 2008 at 04:07:54PM +0300, Michael Tokarev wrote:
> Alasdair G Kergon wrote:
> > On Fri, Feb 15, 2008 at 01:08:21PM +0100, Andi Kleen wrote:
> >> Implement barrier support for single device DM devices
> > Thanks. We've got some (more-invasive) dm patches in the works that
> > attempt to use flushing to emulate barriers where we can't just
> > pass them down like that.
> I wonder if it's worth the effort to try to implement this.
The decision got taken to allocate barrier bios to implement the basic
flush so dm has little choice in this matter now. (If you're going to
implement barriers for flush, you might as well implement them more
generally.)
Maybe I should spell this out more clearly for those who weren't
tracking this block layer change: AFAIK You cannot currently flush a
device-mapper block device without doing some jiggery-pokery.
> For example, how safe
> xfs is if barriers are not supported or turned off?
The last time we tried xfs with dm it didn't seem to notice -EOPNOTSUPP
everywhere it should => recovery may find corruption.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2008-02-19 2:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 12:08 Andi Kleen
2008-02-15 12:20 ` Alasdair G Kergon
2008-02-15 13:07 ` Michael Tokarev
2008-02-15 14:20 ` Andi Kleen
2008-02-15 14:12 ` [dm-devel] " Alasdair G Kergon
2008-02-15 15:34 ` Andi Kleen
2008-02-15 15:31 ` Alan Cox
2008-02-18 12:48 ` Ric Wheeler
2008-02-18 13:24 ` Michael Tokarev
2008-02-18 13:52 ` Ric Wheeler
2008-02-19 2:45 ` Alasdair G Kergon
2008-05-16 19:55 ` Mike Snitzer
2008-05-16 21:48 ` Andi Kleen
2008-02-18 22:16 ` David Chinner
2008-02-19 2:56 ` Alasdair G Kergon
2008-02-19 5:36 ` David Chinner
2008-02-19 9:43 ` Andi Kleen
2008-02-19 7:19 ` Jeremy Higdon
2008-02-19 7:58 ` Michael Tokarev
2008-02-20 13:38 ` Ric Wheeler
2008-02-21 3:29 ` Neil Brown
2008-02-21 3:39 ` Neil Brown
2008-02-17 23:31 ` David Chinner
2008-02-19 2:39 ` Alasdair G Kergon [this message]
2008-02-19 11:12 ` David Chinner
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=20080219023900.GB4066@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=andi@firstfloor.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=mjt@tls.msk.ru \
/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
all inboxes | Powered by JetHome®