lkml.org 
[lkml]   [2010]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCHSET block#for-2.6.36-post] block: replace barrier with sequenced flush
    Hello,

    On 08/13/2010 02:55 PM, Vladislav Bolkhovitin wrote:
    > If requested, I can develop the interface further.

    I still think the benefit of ordering by tag would be marginal at
    best, and what have you guys measured there? Under the current
    framework, there's no easy way to measure full ordered-by-tag
    implementation. The mechanism for filesystems to communicate the
    ordering information (which would be a partially ordered graph) just
    isn't there and there is no way the current usage of ordering-by-tag
    only for barrier sequence can achieve anything close to that level of
    difference.

    Ripping out the original ordering by tag mechanism doesn't amount to
    much. The use of ordering-by-tag was pretty half-assed there anyway.
    If you think exporting full ordering information from filesystem to
    the lower layers is worthwhile, please go ahead. It would be very
    interesting to see how much actual difference it can make compared to
    ordering-by-filesystem and if it's actually better and the added
    complexity is manageable, there's no reason not to do that.

    Thank you.

    --
    tejun


    \
     
     \ /
      Last update: 2010-08-13 15:27    [W:0.041 / U:2.236 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site