On Tue, 9 May 2006, Chris Wright wrote:
> Add "always lock'd" implementations of set_bit, clear_bit and
> change_bit and the corresponding test_and_ functions. Also add
> "always lock'd" implementation of cmpxchg. These give guaranteed
> strong synchronisation and are required for non-SMP kernels running on
> an SMP hypervisor.
Could you explain why this is done and what is exactly meant with "always
looked"? Wh the performance impact?
-
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]
