public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: mingo@elte.hu
Cc: The Doctor What <docwhat@gerf.org>,
	linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: O(1) on powerpc....
Date: 25 Jan 2002 09:11:43 -0500	[thread overview]
Message-ID: <1011967954.3501.17.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0201251651430.9011-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0201251651430.9011-100000@localhost.localdomain>

On Fri, 2002-01-25 at 10:52, Ingo Molnar wrote:

> i think Anton has patches to make PowerPC work - Anton?

We could do some things to generically make the other arches compatible
with the new scheduler, things like:

#define smp_processor_id()	(current->processor)

still need to be fixed (to use ->cpu).  I bet after a trivial
find/replace there is little left to do.

	Robert Love


  reply	other threads:[~2002-01-25 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  6:00 O(1) on powerpc The Doctor What
2002-01-25 15:52 ` Ingo Molnar
2002-01-25 14:11   ` Robert Love [this message]
2002-01-25 16:12     ` Ingo Molnar

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=1011967954.3501.17.camel@phantasy \
    --to=rml@tech9.net \
    --cc=anton@samba.org \
    --cc=docwhat@gerf.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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