public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Rival <frival@zk3.dec.com>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: Mike Kravetz <kravetz@us.ibm.com>,
	lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] NUMA scheduling
Date: Fri, 22 Feb 2002 14:29:46 -0500	[thread overview]
Message-ID: <3C769C2A.80059D73@zk3.dec.com> (raw)
In-Reply-To: <20020222105606.C1575@w-mikek2.des.beaverton.ibm.com> <20020222111404.A1515593@sgi.com>

Ditto.  Maybe I'll even get a chance to check it out on an EV7. ;)

 - Pete

Jesse Barnes wrote:

> On Fri, Feb 22, 2002 at 10:56:06AM -0800, Mike Kravetz wrote:
> > Below is preliminary patch to implement some form of NUMA scheduling
> > on top of Ingo's K3 scheduler patch for 2.4.17.  This is VERY early
> > code and brings up some issues that need to be discussed/explored in
> > more detail.  This patch was created to form a basis for discussion,
> > rather than as a solution.  The patch was created for the i386 based
> > NUMA system I have access to.  It will not work on other architectures.
> > However, the only architecture specific code is a call to initialize
> > some of the NUMA specific scheduling data structures.  Therefore, it
> > should be trivial to port.
>
> Ah, you beat me to it; I was working on code very similar to this when
> I got your e-mail.  I think this sort of thing will address the
> problem we've been seeing on machines with more than 16 cpus or so
> (IDLE_REBALANCE_TICK is too small, flooding CPUs with load_balance
> requests), as well as making numa scheduling a little more efficient.
> I'll see if I can make it work on our platform and let you know how it
> goes.
>
> Jesse
>
> _______________________________________________
> Lse-tech mailing list
> Lse-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lse-tech


  reply	other threads:[~2002-02-22 19:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 18:56 NUMA scheduling Mike Kravetz
2002-02-22 19:14 ` [Lse-tech] " Jesse Barnes
2002-02-22 19:29   ` Peter Rival [this message]
2002-02-22 23:59 ` Mike Kravetz
2002-02-25 18:32 ` Erich Focht
2002-02-25 18:55   ` Martin J. Bligh
2002-02-25 19:03     ` Larry McVoy
2002-02-25 19:28       ` Davide Libenzi
2002-02-25 19:45         ` Davide Libenzi
2002-02-25 19:35       ` Timothy D. Witham
2002-02-25 19:49       ` Bill Davidsen
2002-02-25 20:02         ` Larry McVoy
2002-02-25 20:18           ` Davide Libenzi
2002-02-26  5:14           ` Bill Davidsen
2002-02-25 23:35     ` [Lse-tech] [rebalance at: do_fork() vs. do_execve()] " Andy Pfiffer
2002-02-26 10:33     ` [Lse-tech] " Erich Focht
2002-02-26 15:30       ` Martin J. Bligh
2002-02-27 16:56         ` Erich Focht
2002-02-26 19:03       ` 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=3C769C2A.80059D73@zk3.dec.com \
    --to=frival@zk3.dec.com \
    --cc=jbarnes@sgi.com \
    --cc=kravetz@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