Re: [patch 2.6.15-rc5] Define an ia64 version of __raw_read_trylock

From: Zou Nan hai <nanhai.zou_at_intel.com>
Date: 2005-12-12 17:16:29
On Sat, 2005-12-10 at 11:24, Keith Owens wrote:
> IA64 is using the generic version of __raw_read_trylock, which always
> waits for the lock to be free instead of returning when the lock is in
> use.  Define an ia64 version of __raw_read_trylock which behaves
> correctly, and drop the generic one.
> 
> Signed-off-by: Keith Owens <kaos@sgi.com>
> 
> Index: linux/include/asm-ia64/spinlock.h
> ===================================================================
> --- linux.orig/include/asm-ia64/spinlock.h      2005-12-09
> 14:44:56.883252331 +1100
> +++ linux/include/asm-ia64/spinlock.h   2005-12-10 14:20:44.459423430
> +1100
> @@ -201,6 +201,16 @@ static inline void __raw_write_unlock(ra
>  
>  #endif /* !ASM_SUPPORTED */
>  
> -#define __raw_read_trylock(lock) generic__raw_read_trylock(lock)
> +static inline int __raw_read_trylock(raw_rwlock_t *x)
> +{
> +       union {
> +               raw_rwlock_t lock;
> +               __u32 word;
> +       } old, new;
> +       old.lock = new.lock = *x;
> +       old.lock.write_lock = new.lock.write_lock = 0;
> +       ++new.lock.read_counter;
> +       return (u32)ia64_cmpxchg4_acq((__u32 *)(x), new.word,
> old.word) == old.word;
> +}
>  
>  #endif /*  _ASM_IA64_SPINLOCK_H */
> 

   How about using fetchadd4.acq 1 in trylock and rollback by fetchadd4.rel -1 if lock failed, 
just like how __raw_read_lock does?
   That should emit fewer code and give no extra memory foot print I think.

Zou Nan hai

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Mon Dec 12 18:54:51 2005

This archive was generated by hypermail 2.1.8 : 2005-12-12 18:54:59 EST