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

On Thursday, February 28, 2002 10:55:46 AM -0500 Chris Mason <> wrote:

>> A longer term solution might be to keep the writeback cache but send down a
>> SYNCHRONIZE CACHE command as part of the back end completion of a barrier
>> write, so the fs wouldn't get a completion until the write was done and all
>> the dirty cache blocks flushed to the medium.
> Right, they could just implement ORDERED_FLUSH in the barrier patch.

So, a little testing with scsi_info shows my scsi drives do have
writeback cache on. great. What's interesting is they
must be doing additional work for ordered tags. If they were treating
the block as written once in cache, using the tags should not change
performance at all. But, I can clearly show the tags changing
performance, and hear the drive write pattern change when tags are on.


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:21    [W:0.183 / U:0.212 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site