From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Robert Love <rml@tech9.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
riel@conectiva.com.br
Subject: Re: [PATCH] generalized spin_lock_bit
Date: Sat, 20 Jul 2002 14:15:39 -0700 [thread overview]
Message-ID: <20020720211539.GG1096@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207201335560.1492-100000@home.transmeta.com>
On 20 Jul 2002, Robert Love wrote:
>> The attached patch implements bit-sized spinlocks via the following
>> interfaces:
On Sat, Jul 20, 2002 at 01:40:22PM -0700, Linus Torvalds wrote:
> In particular, with the current pte_chain_lock() interface, it will be
> _trivial_ to turn that bit in page->flags to be instead a hash based on
> the page address into an array of spinlocks. Which is a lot more portable
> than the current code.
> (The current code works, but look at what it generates on old sparcs, for
> example).
I was hoping to devolve the issue of the implementation of it to arch
maintainers by asking for this. I was vaguely aware that the atomic bit
operations are implemented via hashed spinlocks on PA-RISC and some
others, so by asking for the right primitives to come back up from arch
code I hoped those who spin elsewhere might take advantage of their
window of exclusive ownership.
Would saying "Here is an address, please lock it, and if you must flip
a bit, use this bit" suffice? I thought it might give arch code enough
room to wiggle, but is it enough?
Thanks,
Bill
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Robert Love <rml@tech9.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
riel@conectiva.com.br
Subject: Re: [PATCH] generalized spin_lock_bit
Date: Sat, 20 Jul 2002 14:15:39 -0700 [thread overview]
Message-ID: <20020720211539.GG1096@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207201335560.1492-100000@home.transmeta.com>
On 20 Jul 2002, Robert Love wrote:
>> The attached patch implements bit-sized spinlocks via the following
>> interfaces:
On Sat, Jul 20, 2002 at 01:40:22PM -0700, Linus Torvalds wrote:
> In particular, with the current pte_chain_lock() interface, it will be
> _trivial_ to turn that bit in page->flags to be instead a hash based on
> the page address into an array of spinlocks. Which is a lot more portable
> than the current code.
> (The current code works, but look at what it generates on old sparcs, for
> example).
I was hoping to devolve the issue of the implementation of it to arch
maintainers by asking for this. I was vaguely aware that the atomic bit
operations are implemented via hashed spinlocks on PA-RISC and some
others, so by asking for the right primitives to come back up from arch
code I hoped those who spin elsewhere might take advantage of their
window of exclusive ownership.
Would saying "Here is an address, please lock it, and if you must flip
a bit, use this bit" suffice? I thought it might give arch code enough
room to wiggle, but is it enough?
Thanks,
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-07-20 21:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 20:21 [PATCH] generalized spin_lock_bit Robert Love
2002-07-20 20:21 ` Robert Love
2002-07-20 20:40 ` Linus Torvalds
2002-07-20 20:40 ` Linus Torvalds
2002-07-20 21:15 ` William Lee Irwin III [this message]
2002-07-20 21:15 ` William Lee Irwin III
2002-07-20 21:19 ` Robert Love
2002-07-20 21:19 ` Robert Love
2002-07-20 21:20 ` Robert Love
2002-07-20 21:20 ` Robert Love
2002-07-20 23:25 ` Linus Torvalds
2002-07-20 23:25 ` Linus Torvalds
2002-07-20 22:27 ` David S. Miller
2002-07-20 22:27 ` David S. Miller
2002-07-20 22:46 ` Robert Love
2002-07-20 22:46 ` Robert Love
2002-07-21 0:26 ` Alan Cox
2002-07-21 0:26 ` Alan Cox
2002-07-21 1:31 ` David S. Miller
2002-07-21 1:31 ` David S. Miller
2002-07-21 13:48 ` Alan Cox
2002-07-21 13:48 ` Alan Cox
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=20020720211539.GG1096@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.