[lkml]   [2007]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
    [ cc'ing Ric Wheeler for storage array thingie.  Hi, whole thread is at ]

    Hello, wrote:
    > but when you consider the self-contained disk arrays it's an entirely
    > different story. you can easily have a few gig of cache and a complete
    > OS pretending to be a single drive as far as you are concerned.
    > and the price of such devices is plummeting (in large part thanks to
    > Linux moving into this space), you can now readily buy a 10TB array for
    > $10k that looks like a single drive.

    Don't those thingies usually have NV cache or backed by battery such
    that ORDERED_DRAIN is enough?

    The problem is that the interface between the host and a storage device
    (ATA or SCSI) is not built to communicate that kind of information
    (grouped flush, relaxed ordering...). I think battery backed
    ORDERED_DRAIN combined with fine-grained host queue flush would be
    pretty good. It doesn't require some fancy new interface which isn't
    gonna be used widely anyway and can achieve most of performance gain if
    the storage plays it smart.


    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: 2007-06-01 09:21    [W:0.022 / U:39.468 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site