From: Kanoj Sarcar <kanoj@google.engr.sgi.com>
To: mingo@elte.hu
Cc: frankeh@us.ibm.com (Hubertus Franke),
mkravetz@sequent.com (Mike Kravetz),
fabio@chromium.com (Fabio Riccardi),
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 09:39:23 -0700 (PDT) [thread overview]
Message-ID: <200104041639.JAA78761@google.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0104041527190.5382-100000@elte.hu> from "Ingo Molnar" at Apr 04, 2001 03:34:22 PM
>
>
> On Wed, 4 Apr 2001, Hubertus Franke wrote:
>
> > Another point to raise is that the current scheduler does a exhaustive
> > search for the "best" task to run. It touches every process in the
> > runqueue. this is ok if the runqueue length is limited to a very small
> > multiple of the #cpus. [...]
>
> indeed. The current scheduler handles UP and SMP systems, up to 32
> (perhaps 64) CPUs efficiently. Agressively NUMA systems need a different
> approach anyway in many other subsystems too, Kanoj is doing some
> scheduler work in that area.
Actually, not _much_ work has been done in this area. Alongwith a bunch
of other people, I have some ideas about what needs to be done. For
example, for NUMA, we need to try hard to schedule a thread on the
node that has most of its memory (for no reason other than to decrease
memory latency). Independently, some NUMA machines build in multilevel
caches and local snoops that also means that specific processors on
the same node as the last_processor are also good candidates to run
the process next.
To handle a single layer of shared caches, I have tried certain simple
things, mostly as hacks, but am not pleased with the results yet. More
testing needed.
Kanoj
>
> but the original claim was that the scheduling of thousands of runnable
> processes (which is not equal to having thousands of sleeping processes)
> must perform well - which is a completely different issue.
>
> Ingo
>
>
> _______________________________________________
> Lse-tech mailing list
> Lse-tech@lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/lse-tech
>
next prev parent reply other threads:[~2001-04-04 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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 16:39 ` Kanoj Sarcar [this message]
2001-04-04 17:00 ` Andrea Arcangeli
2001-04-04 15:44 ` Khalid Aziz
2001-04-04 15:55 ` [Lse-tech] " Christoph Hellwig
2001-04-04 17:03 Hubertus Franke
2001-04-04 17:14 ` Kanoj Sarcar
2001-04-04 17:34 Hubertus Franke
2001-04-04 17:40 Paul McKenney
2001-04-05 11:14 alad
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=200104041639.JAA78761@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=fabio@chromium.com \
--cc=frankeh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®