From: Linus Torvalds <torvalds@osdl.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Chubb <peterc@gelato.unsw.edu.au>,
Chris Wedgwood <cw@f00f.org>, Andrew Morton <akpm@osdl.org>,
paulus@samba.org, linux-kernel@vger.kernel.org,
tony.luck@intel.com, dsw@gelato.unsw.edu.au,
benh@kernel.crashing.org, linux-ia64@vger.kernel.org,
hch@infradead.org, wli@holomorphy.com, jbarnes@sgi.com
Subject: Re: [patch 1/3] spinlock fix #1, *_can_lock() primitives
Date: Thu, 20 Jan 2005 16:31:11 +0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0501200823010.8178@ppc970.osdl.org> (raw)
In-Reply-To: <20050120160839.GA13067@elte.hu>
On Thu, 20 Jan 2005, Ingo Molnar wrote:
>
> anyway, here's my first patch again, with s/trylock_test/can_lock/.
I don't want to break all the other architectures. Or at least not most of
them. Especially since I was hoping to do a -pre2 soon (well, like today,
but I guess that's out..) and make the 2.6.11 cycle shorter than 2.6.10.
So I'd like to now _first_ get
> spin_can_lock(lock)
> read_can_lock(lock)
> write_can_lock(lock)
for at least most architectures (ie for me at a minimum that is x86,
x86-64, ia64 and ppc64 - and obviously the "always true" cases for the
UP version).
Ok?
Also, I've already made sure that I can't apply any half-measures by
mistake by undoing the mess that it was before, and making sure that any
patches I get have to be "clean slate".
That said, I like how just the _renaming_ of the thing (and making them
all consistent) made your BUILD_LOCK_OPS() helper macro much simpler. So
I'm convinced that this is the right solution - I just want to not screw
up other architectures.
I can do ppc64 myself, can others fix the other architectures (Ingo,
shouldn't the UP case have the read/write_can_lock() cases too? And
wouldn't you agree that it makes more sense to have the rwlock test
variants in asm/rwlock.h?):
Linus
> --- linux/include/linux/spinlock.h.orig
> +++ linux/include/linux/spinlock.h
> @@ -584,4 +584,10 @@ static inline int bit_spin_is_locked(int
> #define DEFINE_SPINLOCK(x) spinlock_t x = SPIN_LOCK_UNLOCKED
> #define DEFINE_RWLOCK(x) rwlock_t x = RW_LOCK_UNLOCKED
>
> +/**
> + * spin_can_lock - would spin_trylock() succeed?
> + * @lock: the spinlock in question.
> + */
> +#define spin_can_lock(lock) (!spin_is_locked(lock))
> +
> #endif /* __LINUX_SPINLOCK_H */
> --- linux/include/asm-i386/spinlock.h.orig
> +++ linux/include/asm-i386/spinlock.h
> @@ -188,6 +188,18 @@ typedef struct {
>
> #define rwlock_is_locked(x) ((x)->lock != RW_LOCK_BIAS)
>
> +/**
> + * read_can_lock - would read_trylock() succeed?
> + * @lock: the rwlock in question.
> + */
> +#define read_can_lock(x) (atomic_read((atomic_t *)&(x)->lock) > 0)
> +
> +/**
> + * write_can_lock - would write_trylock() succeed?
> + * @lock: the rwlock in question.
> + */
> +#define write_can_lock(x) ((x)->lock = RW_LOCK_BIAS)
> +
> /*
> * On x86, we implement read-write locks as a 32-bit counter
> * with the high bit (sign) being the "contended" bit.
>
next prev parent reply other threads:[~2005-01-20 16:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050117055044.GA3514@taniwha.stupidest.org>
[not found] ` <20050116230922.7274f9a2.akpm@osdl.org>
[not found] ` <20050117143301.GA10341@elte.hu>
2005-01-18 1:47 ` Horrible regression with -CURRENT from "Don't busy-lock-loop in preemptable spinlocks" patch Darren Williams
2005-01-18 4:28 ` Darren Williams
2005-01-18 7:08 ` Chris Wedgwood
2005-01-19 0:14 ` Peter Chubb
2005-01-19 8:04 ` Ingo Molnar
2005-01-19 9:18 ` Peter Chubb
2005-01-19 9:20 ` Ingo Molnar
2005-01-19 21:43 ` Paul Mackerras
2005-01-20 2:34 ` [PATCH RFC] 'spinlock/rwlock fixes' V3 [1/1] Chris Wedgwood
2005-01-20 3:01 ` Andrew Morton
2005-01-20 3:18 ` Chris Wedgwood
2005-01-20 3:33 ` Andrew Morton
2005-01-20 8:59 ` Peter Chubb
2005-01-20 13:04 ` Ingo Molnar
2005-01-20 15:51 ` Linus Torvalds
2005-01-20 16:08 ` [patch 1/3] spinlock fix #1, *_can_lock() primitives Ingo Molnar
2005-01-20 16:11 ` [patch 2/3] spinlock fix #2: generalize [spin|rw]lock yielding Ingo Molnar
2005-01-20 16:12 ` [patch 3/3] spinlock fix #3: type-checking spinlock primitives, x86 Ingo Molnar
2005-01-20 16:14 ` [patch] stricter type-checking rwlock " Ingo Molnar
2005-01-20 16:16 ` [patch] minor spinlock cleanups Ingo Molnar
2005-01-20 16:31 ` Linus Torvalds [this message]
2005-01-20 16:40 ` [patch 1/3] spinlock fix #1, *_can_lock() primitives Ingo Molnar
2005-01-20 17:48 ` Linus Torvalds
2005-01-20 17:53 ` Ingo Molnar
2005-01-20 18:22 ` [patch, BK-curr] nonintrusive spin-polling loop in kernel/spinlock.c Ingo Molnar
2005-01-20 18:25 ` [patch, BK-curr] rename 'lock' to 'slock' in asm-i386/spinlock.h Ingo Molnar
2005-01-20 23:45 ` [patch, BK-curr] nonintrusive spin-polling loop in kernel/spinlock.c Linus Torvalds
2005-01-20 16:44 ` [patch 1/3] spinlock fix #1, *_can_lock() primitives Ingo Molnar
2005-01-20 16:59 ` Ingo Molnar
2005-01-20 16:47 ` Ingo Molnar
2005-01-20 16:57 ` Ingo Molnar
2005-01-20 16:05 ` [PATCH RFC] 'spinlock/rwlock fixes' V3 [1/1] Linus Torvalds
2005-01-20 16:20 ` Ingo Molnar
2005-01-20 16:18 ` Linus Torvalds
2005-01-20 16:23 ` Ingo Molnar
2005-01-20 17:30 ` Linus Torvalds
2005-01-20 17:38 ` Ingo Molnar
2005-01-20 16:28 ` Ingo Molnar
2005-01-20 5:49 ` Horrible regression with -CURRENT from "Don't busy-lock-loop in preemptable spinlocks" patch Grant Grundler
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=Pine.LNX.4.58.0501200823010.8178@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=cw@f00f.org \
--cc=dsw@gelato.unsw.edu.au \
--cc=hch@infradead.org \
--cc=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterc@gelato.unsw.edu.au \
--cc=tony.luck@intel.com \
--cc=wli@holomorphy.com \
/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