From: Oliver Neukum <oliver@neukum.org>
To: "jidong xiao" <jidong.xiao@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-kernel]Why there are so many struct rw_semaphore being defined?
Date: Wed, 4 Jul 2007 11:15:06 +0200 [thread overview]
Message-ID: <200707041115.06233.oliver@neukum.org> (raw)
In-Reply-To: <4104961b0707040207r7fd9054bvfd33830827102acf@mail.gmail.com>
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.
Regards
Oliver
next prev parent reply other threads:[~2007-07-04 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 9:07 [linux-kernel]Why there are so many struct rw_semaphore being defined? jidong xiao
2007-07-04 9:15 ` Oliver Neukum [this message]
2007-07-04 10:34 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707041115.06233.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=jidong.xiao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox