On Fri, Jul 14, 2006 at 04:05:01PM -0400, Steven Rostedt wrote:
> There are some more advanced barrier functions:
>
> (*) set_mb(var, value)
> - (*) set_wmb(var, value)
>
> - These assign the value to the variable and then insert at least a write
> - barrier after it, depending on the function. They aren't guaranteed to
> + This assigns the value to the variable and then inserts at least a write
> + barrier after it, depending on the function. It isn't guaranteed to
> insert anything more than a compiler barrier in a UP compilation.
"There is one more advanced barrier function"? ;-) Or did you want to
remove set_mb()?
Plus, the "depending on the function" bit means "respectively". So what
you really want as help is something like:
This assigns the value to the variable and then inserts a
barrier after the assignment. It isn't guaranteed to insert
anything more than a compiler barrier in a UP compilation.
-
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
