From: "David S. Miller" <davem@redhat.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-arch@vger.kernel.org, mingo@redhat.com
Subject: Re: [RFC][PATCH] Consolidate architecture context switch locking
Date: Sat, 29 May 2004 23:28:02 -0700 [thread overview]
Message-ID: <20040529232802.24a367c7.davem@redhat.com> (raw)
In-Reply-To: <40B94D79.8090903@yahoo.com.au>
On Sun, 30 May 2004 12:56:57 +1000
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Those that do need to define TIF_RUNNING, which I haven't done
> in the patch.
How come we can't use a spinlock like the existing instances
did? A spinlock should be cheaper than a SMP atomic bitop
on at least some such platforms. It is on sparc at least.
next prev parent reply other threads:[~2004-05-30 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 2:56 [RFC][PATCH] Consolidate architecture context switch locking Nick Piggin
2004-05-30 6:28 ` David S. Miller [this message]
2004-05-30 7:00 ` 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=20040529232802.24a367c7.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox