From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.3 _raw_write_trylock and __down_write_trylock
Date: Mon, 23 Feb 2004 19:53:42 +0000 [thread overview]
Message-ID: <16442.23110.704083.5403@napali.hpl.hp.com> (raw)
In-Reply-To: <2402.1077498957@kao2.melbourne.sgi.com>
>>>>> On Mon, 23 Feb 2004 12:15:57 +1100, Keith Owens <kaos@sgi.com> said:
Keith> 2.6.3 defines include/asm-ia64/spinlock.h::_raw_write_trylock
Keith> (both asm and C versions) and
Keith> include/asm-ia64/rwsem.h::__down_write_trylock.
Keith> The C version of _raw_write_trylock is functionally identical
Keith> to __down_write_trylock, but the code is completely
Keith> different. Why have two implementations with such radically
Keith> different code for the same feature? Why have both a C and
Keith> asm version of _raw_write_trylock when the C version will
Keith> work everywhere?
rwsem.h implements read-write semaphores, spinlock.h implements
read-write spinlocks.
GCC doesn't schedule the C code for _raw_write_lock() well, hence the
explicit ASM-version.
--david
prev parent reply other threads:[~2004-02-23 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 1:15 2.6.3 _raw_write_trylock and __down_write_trylock Keith Owens
2004-02-23 19:53 ` David Mosberger [this message]
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=16442.23110.704083.5403@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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