[email protected] wrote:
The right thing to do here is to wait for the flag to be set *outside*
the lock, and then re-validate inside the lock:
This may work on some processors, but on others the read of "progress"
in XXX, or the write in YYY may require arch-specific code to force the
update out to other cpus.
Alternately, explicitly atomic operations should suffice, but a simple
increment is probably not enough for portable code.
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
