[lkml]   [2001]   [Oct]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [POT] Which journalised filesystem ?

    On Fri, Oct 05, 2001 at 03:57:49PM +0100, Alan Cox wrote:
    > > > We (as in Linux) should make sure that we explicitly tell the disk when
    > > > we need it to flush its disk buffers. We don't do that right, and
    > > > because of _our_ problems some people claim that writeback caching is
    > > > evil and bad.
    > >
    > > Does this even work right for IDE ?
    > Current IDE drives it may be a NOP. Worse than that it would totally ruin
    > high end raid performance. We need to pass write barriers. A good i2o card
    > might have 256Mb of writeback cache that we want to avoid flushing - because
    > it is battery backed and can be ordered.

    The important thing is to flush to non-volatile storage: non-volatile
    cache still qualifies. The one thing we need to avoid is the data
    lingering in volatile cache, and that's a different thing.

    Sure, journaling filesystems can benefit from a write barrier, but at
    some point that's not sufficient --- we really need to know, at a high
    level, whether the data is permanently secured. When your MTA
    finishes its fsync(), it assumes that the mail spool file has been
    securely stored and it can tell the sender to go ahead and delete the
    upstream copy.

    A barrier is not sufficient there. It's a useful primitive to have,
    but not a substitute for a flush to permanent storage.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:08    [W:0.051 / U:1.460 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site