[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49CD394B.9080903@garzik.org>
Date: Fri, 27 Mar 2009 16:38:35 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Christoph Hellwig <hch@...radead.org>
CC: Theodore Tso <tytso@....edu>, Jens Axboe <jens.axboe@...cle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Arjan van de Ven <arjan@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Nick Piggin <npiggin@...e.de>, David Rees <drees76@...il.com>,
Jesper Krogh <jesper@...gh.cc>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.29
Christoph Hellwig wrote:
> And please add a tuneable for the flush. Preferable a generic one at
> the block device layer instead of the current mess where every
> filesystem has a slightly different option for barrier usage.
At the very least, IMO the block layer should be able to notice when
barriers need not be translated into cache flushes. Most notably when
wb cache is disabled on the drive, something easy to auto-detect, but
probably a manual switch also, for people with enterprise battery-backed
storage and such.
Jeff
--
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