public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid@fc.hp.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Hubertus Franke <frankeh@us.ibm.com>,
	mingo@elte.hu, Mike Kravetz <mkravetz@sequent.com>,
	Fabio Riccardi <fabio@chromium.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: a quest for a better scheduler
Date: Wed, 04 Apr 2001 09:49:12 -0600	[thread overview]
Message-ID: <3ACB4278.2E4F48C0@fc.hp.com> (raw)
In-Reply-To: <OFB30A8B18.2E3AD16C-ON85256A24.004BD696@pok.ibm.com> <20010404171227.W20911@athlon.random>

Andrea Arcangeli wrote:
> 
> On Wed, Apr 04, 2001 at 10:03:10AM -0400, Hubertus Franke wrote:
> > I understand the dilemma that the Linux scheduler is in, namely satisfy
> > the low end at all cost. [..]
> 
> We can satisfy the low end by making the numa scheduler at compile time (that's
> what I did in my patch at least).
> 
> Andrea

I fully agree with this approach. It would be very hard to design a
scheduler that performs equally well on a UP machine running couple of
processes and a NUMA machine. These two cases represent the two ends of
spectrum. The two schedulers should be separate IMO and one of them
should be selected at compile time.

--
Khalid
 
====================================================================
Khalid Aziz                             Linux Development Laboratory
(970)898-9214                                        Hewlett-Packard
khalid@fc.hp.com                                    Fort Collins, CO

  reply	other threads:[~2001-04-04 15:50 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 14:03 a quest for a better scheduler Hubertus Franke
2001-04-04 13:23 ` Ingo Molnar
2001-04-04 22:16   ` Tim Wright
2001-04-04 22:54     ` Christopher Smith
2001-04-05 22:38       ` Timothy D. Witham
2001-04-06  3:27         ` Christopher Smith
2001-04-06 18:06         ` Timothy D. Witham
2001-04-06 21:08           ` Michael Peddemors
2001-04-06 22:33           ` Nathan Straz
2001-04-04 15:12 ` Andrea Arcangeli
2001-04-04 15:49   ` Khalid Aziz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-18 14:50 Yoav Etsion
2001-04-06 13:15 Hubertus Franke
2001-04-05 23:53 Torrey Hoffman
2001-04-05 23:01 Hubertus Franke
2001-04-04 19:06 Hubertus Franke
2001-04-04 17:17 Hubertus Franke
2001-04-04 15:36 Hubertus Franke
2001-04-04 15:28 Hubertus Franke
2001-04-04 13:43 Hubertus Franke
2001-04-04 13:25 ` Ingo Molnar
2001-04-04 13:34 ` Ingo Molnar
2001-04-04 15:08   ` Andrea Arcangeli
2001-04-04 15:44 ` Khalid Aziz
2001-04-04  6:36 alad
2001-04-03  2:23 Fabio Riccardi
2001-04-03  8:55 ` Ingo Molnar
2001-04-03 19:13   ` Mike Kravetz
2001-04-03 18:47     ` Ingo Molnar
2001-04-03 22:43       ` Mike Kravetz
2001-04-04  0:18         ` Fabio Riccardi
2001-04-04  2:47           ` Mike Kravetz
2001-04-04  4:21             ` Fabio Riccardi
2001-04-04 17:27               ` Mike Kravetz
2001-04-04  6:53           ` Ingo Molnar
2001-04-04 16:12             ` Davide Libenzi
2001-04-04  6:28         ` Ingo Molnar
2001-04-03 12:31 ` Alan Cox
2001-04-04  0:33   ` Fabio Riccardi
2001-04-04  0:35     ` Alan Cox
2001-04-04  1:17       ` Fabio Riccardi
2001-04-04  1:50         ` Christopher Smith
2001-04-04 11:57       ` Ingo Molnar
2001-04-04 11:51     ` 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=3ACB4278.2E4F48C0@fc.hp.com \
    --to=khalid@fc.hp.com \
    --cc=andrea@suse.de \
    --cc=fabio@chromium.com \
    --cc=frankeh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mkravetz@sequent.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