public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Mike Kravetz <mkravetz@sequent.com>,
	Linus Torvalds <torvalds@transmeta.com>
Cc: Hubertus Franke <frankeh@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Scalable Scheduling
Date: Wed, 8 Aug 2001 21:06:01 +0200	[thread overview]
Message-ID: <0108082106010A.00351@starship> (raw)
In-Reply-To: <Pine.LNX.4.33.0108081041260.8047-100000@penguin.transmeta.com> <Pine.LNX.4.33.0108081058420.8103-100000@penguin.transmeta.com> <20010808112800.F1088@w-mikek2.des.beaverton.ibm.com>
In-Reply-To: <20010808112800.F1088@w-mikek2.des.beaverton.ibm.com>

On Wednesday 08 August 2001 20:28, Mike Kravetz wrote:
> Yes we have, we'll provide those numbers with the updated patch.
> One challenge will be maintaining the same level of performance
> for UP as in the current code.  The current code has #ifdefs to
> separate some of the UP/SMP code paths and we will try to eliminate
> these.

Does it help if I clarify what Linus was suggesting?  Instead of:

         #ifdef CONFIG_SMP
                 .. use nr_running() ..
         #else
                 .. use nr_running ..
         #endif

write:

	inline int nr_running(void)
	{
	#ifdef CONFIG_SMP
		int i = 0, tot=nt_running(REALTIME_RQ);
		while (i < smp_num_cpus) {
			tot += nt_running(cpu_logical_map(i++));
		}
		return(tot);
	#else
		return nr_running;
	#endif
	}

Then see if you can make the #ifdef's go away from that too.  (If that's 
too hard, well, at least the #ifdef's are now reduced.)

--
Daniel

  reply	other threads:[~2001-08-08 19:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 17:32 [RFC][PATCH] Scalable Scheduling Hubertus Franke
2001-08-08 17:43 ` Linus Torvalds
2001-08-08 18:00   ` Linus Torvalds
2001-08-08 18:18     ` Larry McVoy
2001-08-08 18:53       ` David S. Miller
2001-08-10 23:58         ` Chris Wedgwood
2001-08-08 18:28     ` Mike Kravetz
2001-08-08 19:06       ` Daniel Phillips [this message]
2001-08-08 19:14         ` Linus Torvalds
2001-08-08 19:27       ` Victor Yodaiken
  -- strict thread matches above, loose matches on Subject: below --
2001-08-14 14:22 Erik Corry
2001-08-11  0:04 Hubertus Franke
2001-08-08 20:02 Hubertus Franke
2001-08-08 19:40 Hubertus Franke
2001-08-08 19:51 ` Victor Yodaiken
2001-08-08 19:16 Hubertus Franke
2001-08-08 19:05 Hubertus Franke
2001-08-08 16:16 Mike Kravetz
2001-08-08 16:40 ` Linus Torvalds
2001-08-08 17:05   ` Mike Kravetz

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=0108082106010A.00351@starship \
    --to=phillips@bonn-fries.net \
    --cc=frankeh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkravetz@sequent.com \
    --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