From: Roman Zippel <zippel@linux-m68k.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-arch@vger.kernel.org, Christoph Lameter <clameter@sgi.com>
Subject: Re: Better local_t implementation needed
Date: Fri, 20 Apr 2007 23:25:04 +0200 [thread overview]
Message-ID: <200704202325.06301.zippel@linux-m68k.org> (raw)
In-Reply-To: <200704201256.13008.ak@suse.de>
Hi,
On Friday 20 April 2007 12:56, Andi Kleen wrote:
> There used to be a portable implementation of local.h
> that instead defines local_t as a two value array
> indexed by in_interrupt(). I'm considering to add that back.
That doesn't really work in general, interrupts can interrupt other
interrupts.
bye, Roman
next prev parent reply other threads:[~2007-04-20 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 10:56 Better local_t implementation needed Andi Kleen
2007-04-20 16:10 ` Christoph Lameter
2007-04-20 17:01 ` Andi Kleen
2007-04-20 17:05 ` Christoph Lameter
2007-04-20 18:31 ` Luck, Tony
2007-04-20 20:14 ` Andi Kleen
2007-04-20 20:27 ` Christoph Lameter
2007-04-20 21:25 ` Roman Zippel [this message]
2007-04-20 22:39 ` David Miller
2007-04-21 0:25 ` Christoph Lameter
2007-04-21 4:45 ` David Miller
[not found] <617E1C2C70743745A92448908E030B2A015F2392@scsmsx411.amr.corp.intel.com>
2007-04-20 20:38 ` Christoph Lameter
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=200704202325.06301.zippel@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-arch@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;
as well as URLs for NNTP newsgroup(s).