From: Rusty Russell <rusty@rustcorp.com.au>
To: <mingo@elte.hu>
Cc: James.Bottomley@HansenPartnership.com,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Problems with O(1) scheduler on non-x86 arch's
Date: Fri, 18 Jan 2002 13:23:59 +1100 [thread overview]
Message-ID: <20020118132359.3cbca3f3.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0201171046480.2000-100000@localhost.localdomain>
In-Reply-To: <200201170229.g0H2TnY04563@localhost.localdomain> <Pine.LNX.4.33.0201171046480.2000-100000@localhost.localdomain>
On Thu, 17 Jan 2002 10:50:58 +0100 (CET)
Ingo Molnar <mingo@elte.hu> wrote:
> in the long term i think the correct approach would be to always store the
> logical CPU number in p->cpu.
The hotplug CPU patch gets rid of the whole concept of "logical CPU number".
This is even cleaner, and avoids these mistakes which bite us all the time.
http://www.kernel.org/pub/linux/kernel/people/rusty/patches/Hotcpu
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2002-01-18 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 2:29 Problems with O(1) scheduler on non-x86 arch's James Bottomley
2002-01-17 9:50 ` Ingo Molnar
2002-01-17 14:57 ` James Bottomley
2002-01-18 2:23 ` Rusty Russell [this message]
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=20020118132359.3cbca3f3.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox