[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090214153626.GA3973@infradead.org>
Date: Sat, 14 Feb 2009 10:36:26 -0500
From: Christoph Hellwig <hch@...radead.org>
To: Jeff Garzik <jeff@...zik.org>
Cc: Eric Sandeen <sandeen@...hat.com>,
Fernando Luis V?zquez Cao <fernando@....ntt.co.jp>,
Jan Kara <jack@...e.cz>, Theodore Tso <tytso@....EDU>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Pavel Machek <pavel@...e.cz>,
kernel list <linux-kernel@...r.kernel.org>,
Jens Axboe <jens.axboe@...cle.com>, fernando@....ac.jp,
Ric Wheeler <rwheeler@...hat.com>
Subject: Re: vfs: Add MS_FLUSHONFSYNC mount flag
On Thu, Feb 12, 2009 at 12:29:52PM -0500, Jeff Garzik wrote:
>> The block device *could* choose to ignore this in hardware if it knows
>> it's built with a nonvolatile write cache or if it has no write cache.
>
> That would certainly be my preference -- turn this ON by default, and
> them if a layer NEEDS to ignore it, it can.
Yeah, and we should integrate this with the barriers settings.
I think the right setup is:
- each gendisk has a variable to indicate if we have a write-back
cache, which is filled from scsi inquiry data (or whatever the
equivalent in the storage protocol is), but we allow an override
from userspace if the admin knows better (if he really does or
wants to play fast and lose is the admin's business)
- filesystems do the right things by using barriers and cache flushes
if they see the underlying device needs it.
--
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