public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: frankeh@us.ibm.com (Hubertus Franke)
Cc: linux-kernel@vger.kernel.org (Linux Kernel List),
	lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: a quest for a better scheduler
Date: Wed, 4 Apr 2001 10:14:28 -0700 (PDT)	[thread overview]
Message-ID: <200104041714.KAA43960@google.engr.sgi.com> (raw)
In-Reply-To: <OF5E9EE337.4E94D8F7-ON85256A24.005D15F8@pok.ibm.com> from "Hubertus Franke" at Apr 04, 2001 01:03:32 PM

> 
> 
> 
> Kanoj, our cpu-pooling + loadbalancing allows you to do that.
> The system adminstrator can specify at runtime through a
> /proc filesystem interface the cpu-pool-size, whether loadbalacing
> should take place.

Yes, I think this approach can support the various requirements
put on the scheduler.

I think there are two degrees of freedom that are needed in the
scheduler. One, as you say, for the sysadmin to be able to specify
what overall scheduler behavior he wants. 

Secondly, from the kernel standpoint, there needs to be perarch
hooks, to be able to utilize nodelevel/multilevel caches, NUMA
aspects etc.

Kanoj

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04 17:03 [Lse-tech] Re: a quest for a better scheduler Hubertus Franke
2001-04-04 17:14 ` Kanoj Sarcar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-05 11:14 alad
2001-04-04 17:40 Paul McKenney
2001-04-04 17:34 Hubertus Franke
2001-04-04 15:08 Andrea Arcangeli
2001-04-04 16:50 ` [Lse-tech] " Kanoj Sarcar
2001-04-04 17:16   ` Andrea Arcangeli
2001-04-04 17:49     ` Kanoj Sarcar
2001-04-04 18:00       ` Andrea Arcangeli
2001-04-05 11:13         ` Zdenek Kabelac
2001-04-04 13:43 Hubertus Franke
2001-04-04 15:44 ` Khalid Aziz
2001-04-04 15:55   ` [Lse-tech] " Christoph Hellwig
2001-04-04 13:34 Ingo Molnar
2001-04-04 16:39 ` [Lse-tech] " Kanoj Sarcar
2001-04-04 17:00   ` Andrea Arcangeli

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=200104041714.KAA43960@google.engr.sgi.com \
    --to=kanoj@google.engr.sgi.com \
    --cc=frankeh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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