[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4758.1184110800@turing-police.cc.vt.edu>
Date: Tue, 10 Jul 2007 19:40:00 -0400
From: Valdis.Kletnieks@...edu
To: ric@....com
Cc: Tejun Heo <htejun@...il.com>, david@...g.hm,
Stefan Bader <Stefan.Bader@...ibm.com>,
Phillip Susi <psusi@....rr.com>,
device-mapper development <dm-devel@...hat.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>,
Andreas Dilger <adilger@...sterfs.com>
Subject: Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
On Tue, 10 Jul 2007 14:39:41 EDT, Ric Wheeler said:
> All of the high end arrays have non-volatile cache (read, on power loss, it is a
> promise that it will get all of your data out to permanent storage). You don't
> need to ask this kind of array to drain the cache. In fact, it might just ignore
> you if you send it that kind of request ;-)
OK, I'll bite - how does the kernel know whether the other end of that
fiberchannel cable is attached to a DMX-3 or to some no-name product that
may not have the same assurances? Is there a "I'm a high-end array" bit
in the sense data that I'm unaware of?
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists