From: Rusty Russell <rusty@rustcorp.com.au>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] per-cpu areas for 2.5.3-pre6
Date: Wed, 30 Jan 2002 11:44:02 +1100 [thread overview]
Message-ID: <E16Vir4-0005rs-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Tue, 29 Jan 2002 18:20:44 MDT." <Pine.LNX.4.44.0201291813110.25443-100000@waste.org>
In message <Pine.LNX.4.44.0201291813110.25443-100000@waste.org> you write:
> Yes, obviously.
Um... if it was so "obvious" why did you suggest it in the first
place? 8)
> Nearly as good would be replacing the current logic for figuring out the
> current processor id through current with logic to access the per-cpu
> data. The primary use of that id is indexing that data anyway.
And if you'd been reading this thread, you would have already seen
this idea, and if you'd read the x86 code, you'd have realised that
the tradeoff is arch-specific.
But thanks anyway: what this list really needs is more armchair kernel
hackers discussing code they haven't really thought about.
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-01-30 0:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 9:01 Rusty Russell
2002-01-29 9:22 ` Andrew Morton
2002-01-29 22:09 ` Rusty Russell
2002-01-29 22:21 ` Andrew Morton
2002-01-30 0:48 ` Rusty Russell
2002-01-30 0:49 ` Andrew Morton
2002-01-30 2:00 ` Rusty Russell
2002-01-30 2:12 ` Linus Torvalds
2002-01-30 4:13 ` Rusty Russell
2002-01-30 8:22 ` Richard Henderson
2002-01-30 22:45 ` Rusty Russell
2002-01-31 5:49 ` Richard Henderson
2002-02-01 8:56 ` Rusty Russell
2002-02-01 16:52 ` Richard Henderson
2002-01-29 23:17 ` Oliver Xymoron
2002-01-29 23:36 ` Linus Torvalds
2002-01-30 0:20 ` Oliver Xymoron
2002-01-30 0:44 ` Rusty Russell [this message]
2002-01-30 7:00 ` Oliver Xymoron
2002-01-30 19:43 ` Oliver Xymoron
2002-01-30 23:00 ` Rusty Russell
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=E16Vir4-0005rs-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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
all inboxes | Powered by JetHome®