[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070530104115.GO25091@agk.fab.redhat.com>
Date: Wed, 30 May 2007 11:41:15 +0100
From: Alasdair G Kergon <agk@...hat.com>
To: device-mapper development <dm-devel@...hat.com>
Cc: Stefan Bader <sbader3@...glemail.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>,
David Chinner <dgc@....com>, Phillip Susi <psusi@....rr.com>,
Stefan Bader <Stefan.Bader@...ibm.com>,
Andreas Dilger <adilger@...sterfs.com>,
Tejun Heo <htejun@...il.com>
Subject: Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
On Wed, May 30, 2007 at 11:12:37AM +0200, Stefan Bader wrote:
> it might be better to indicate -EOPNOTSUPP right from
> device-mapper.
Indeed we should. For support, on receipt of a barrier, dm core should
send a zero-length barrier to all active underlying paths, and delay
mapping any further I/O.
Alasdair
--
agk@...hat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists