lkml.org 
[lkml]   [2002]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] 2.4.x write barriers (updated for ext3)
On Mar 3, 11:11pm, Daniel Phillips wrote:
> I have a standing offer from at least one engineer to make firmware changes
> to the drives if it makes Linux work better. So a reasonable plan is: first
> know what's ideal, second ask for it. Coupled with that, we'd need a way of
> identifying drives that don't work in the ideal way, and require a fallback.
>
> In my opinion, the only correct behavior is a write barrier that completes
> when data is on the platter, and that does this even when write-back is
> enabled. Surely this is not rocket science at the disk firmware level. Is
> this or is this not the way ordered tags were supposed to work?


Ordered tags just specify ordering in the command stream. The WCE bit
specifies when the write command is complete. I have never heard of
any implied requirement to flush to media when a drive receives an
ordered tag and WCE is set. It does seem like a useful feature to have
in the standard, but I don't think it's there.

So if one vendor implements those semantics, but the others don't where
does that leave us?

jeremy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [from the cache]
©2003-2011 Jasper Spaans