[lkml]   [2002]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] 2.4.x write barriers (updated for ext3)

    On Mon, Mar 04, 2002 at 11:35:24AM -0600, James Bottomley wrote:

    > Have there been any published comparisons of a write barrier implementation
    > verses something like the McKusick soft update idea

    Soft updates are just another mechanism of doing ordered writes. If
    the disk IO subsystem is lying about write ordering or is doing
    unexpected writeback caching, soft updates are no more of a cure than

    > or even just
    > multi-threaded back end completion of the transactions?

    ext3 already does the on-disk transaction complete asynchronously
    within a separate kjournald thread, independent of writeback IO going
    on in the VM's own writeback threads. Given that it is kernel code
    given full access to the kernel's internal lazy IO completion
    mechanisms, I'm not sure that it can usefully be given any more
    threading. I think the reiserfs situation is similar.

    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:24    [W:0.028 / U:2.100 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site