linux-kernel - Re: Why there are so many struct rw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <468B77A8.9020504@s5r6.in-berlin.de>
Date:	Wed, 04 Jul 2007 12:34:16 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Oliver Neukum <oliver@...kum.org>
CC:	jidong xiao <jidong.xiao@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Why there are so many struct rw_semaphore being
 defined?

Oliver Neukum wrote:
> Am Mittwoch, 4. Juli 2007 schrieb jidong xiao:
>> I see struct rw_semaphore is defined in
>> include/linux/rwsem-spinlock.h,in the meanwhile, I also can find it in
> 
> Quote:
> 
> #ifndef _LINUX_RWSEM_H
> #error "please don't include linux/rwsem-spinlock.h directly, use linux/rwsem.h instead"
> #endif
> 
>> include/asm-**/rwsem.h,for
>> example,include/asm-i386/rwsem.h,include/asm-x86_64/rwsem.h,why?which
>> one should be used?
> 
> This structure is so important to performance that some architectures
> have version optimized to their features.

...but of course we generally include linux/rwsem.h instead of
architecture-specific header files.  linux/rwsem.h will transparently
pull in the optimized variants for us.  (It's evident from the source.)
-- 
Stefan Richter
-=====-=-=== -=== --=--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/