From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] implement ia64 specific mutex primitives
Date: Thu, 12 Jan 2006 00:14:26 +0000 [thread overview]
Message-ID: <20865.1137024866@ocs3.ocs.com.au> (raw)
In-Reply-To: <200601112324.k0BNOog01764@unix-os.sc.intel.com>
"Chen, Kenneth W" (on Wed, 11 Jan 2006 15:24:50 -0800) wrote:
>Implement ia64 optimized mutex primitives. It properly uses
>acquire/release memory ordering semantics in lock/unlock path.
>#define __mutex_fastpath_lock(count, fail_fn) \
>static inline int
>__mutex_fastpath_lock_retval(atomic_t *count, int (*fail_fn)(atomic_t *))
>#define __mutex_fastpath_unlock(count, fail_fn) \
>static inline int
>__mutex_fastpath_trylock(atomic_t *count, int (*fail_fn)(atomic_t *))
Instead of mixing #define and static, make them all static and let gcc
decide if you should inline them. Or make them all #define. Either
works but is more consistent.
next prev parent reply other threads:[~2006-01-12 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 23:24 [patch] implement ia64 specific mutex primitives Chen, Kenneth W
2006-01-12 0:14 ` Keith Owens [this message]
2006-01-12 1:11 ` Chen, Kenneth W
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=20865.1137024866@ocs3.ocs.com.au \
--to=kaos@sgi.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