From: William Lee Irwin III <wli@holomorphy.com>
To: Andi Kleen <ak@suse.de>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
"David S. Miller" <davem@davemloft.net>,
anton@samba.org, linux-arch@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Peter Keilty <Peter.Keilty@hp.com>
Subject: Re: Global spinlock vs local bit spin locks
Date: Fri, 17 Jun 2005 02:15:26 -0700 [thread overview]
Message-ID: <20050617091526.GH3913@holomorphy.com> (raw)
In-Reply-To: <20050617085426.GK31127@wotan.suse.de>
>> As far as page flags go - I agree but I didn't want to use one up.
>> This is very localised and I don't think it is particularly worse
>> than what was there before, so I think we can get away with it for
>> the moment.
On Fri, Jun 17, 2005 at 10:54:26AM +0200, Andi Kleen wrote:
> I'm starting to think that we need different strategies on 32bit
> and 64bit here. 64bit has plenty of bits left; it is just 32bit
> that is a problem here.
Well, there are 3 bits destined to die as things stand now (2 swsusp
via sideband bitmaps and PG_reserved) so the immediate 32-bit shortage
does have a resolution in sight.
-- wli
next prev parent reply other threads:[~2005-06-17 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 4:21 Global spinlock vs local bit spin locks Nick Piggin
2005-06-17 4:45 ` Andrew Morton
2005-06-17 8:50 ` Andi Kleen
2005-06-17 4:45 ` David S. Miller
2005-06-17 4:46 ` William Lee Irwin III
2005-06-17 4:52 ` Andrew Morton
2005-06-17 8:35 ` Nick Piggin
2005-06-17 8:45 ` William Lee Irwin III
2005-06-17 9:21 ` Nick Piggin
2005-06-17 9:28 ` William Lee Irwin III
2005-06-17 8:54 ` Andi Kleen
2005-06-17 9:15 ` William Lee Irwin III [this message]
2005-06-17 9:27 ` Nick Piggin
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=20050617091526.GH3913@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Peter.Keilty@hp.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.