[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49A1E3EB.8050708@garzik.org>
Date: Sun, 22 Feb 2009 18:46:51 -0500
From: Jeff Garzik <jeff@...zik.org>
To: Theodore Tso <tytso@....edu>
CC: Pavel Machek <pavel@....cz>, Eric Sandeen <sandeen@...hat.com>,
Jan Kara <jack@...e.cz>,
Fernando Luis V?zquez Cao <fernando@....ntt.co.jp>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
kernel list <linux-kernel@...r.kernel.org>,
Jens Axboe <jens.axboe@...cle.com>, fernando@....ac.jp,
Ric Wheeler <rwheeler@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: vfs: Add MS_FLUSHONFSYNC mount flag
Jeff Garzik wrote:
> Correctness should come before performance. Linux has not had
> credibility here, in the ATA+ext[23] space at least, and it is
> embarrassing.
To be more clear / precise, this means actually performing the
guarantees we claim to the user. For example,
fsync(2) on ext2 should trigger a storage device writeback cache flush
[or equivalent guarantee via FUA].
fsync(2) or journal commit on ext3 should trigger a flush [or equivalent
guarantee via FUA].
Though, certainly, the user should be able to disable this strict
behavior and trade correctness for performance.
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