On Wed, 29 Mar 2006, Nick Piggin wrote: > However, I think it might be reaonsable to use bit lock operations for > in places like page lock and buffer lock (ie. with acquire and relese > semantics). It improves ia64 without harming other architectures, and > also makes the code more expressive. How would be express the acquire and release semantics? - 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/
- Follow-Ups:
- Re: Fix unlock_buffer() to work the same way as bit_unlock()
- From: Nick Piggin <nickpiggin@yahoo.com.au>
- Re: Fix unlock_buffer() to work the same way as bit_unlock()
- References:
- RE: Fix unlock_buffer() to work the same way as bit_unlock()
- From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
- Re: Fix unlock_buffer() to work the same way as bit_unlock()
- From: Zoltan Menyhart <Zoltan.Menyhart@free.fr>
- Re: Fix unlock_buffer() to work the same way as bit_unlock()
- From: Christoph Lameter <clameter@sgi.com>
- Re: Fix unlock_buffer() to work the same way as bit_unlock()
- From: Nick Piggin <nickpiggin@yahoo.com.au>
- RE: Fix unlock_buffer() to work the same way as bit_unlock()
- Prev by Date: Re: BUG in Linux 2.6.16/2.6.16.1 (compilation failure of third party software)
- Next by Date: [PATCH 0/3] msi abstractions and support for altix
- Previous by thread: Re: Fix unlock_buffer() to work the same way as bit_unlock()
- Next by thread: Re: Fix unlock_buffer() to work the same way as bit_unlock()
- Index(es):
![]() |