mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Michael Hohnbaum <hohnbaum@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [patch] "fully HT-aware scheduler" support, 2.5.31-BK-curr
Date: Wed, 4 Sep 2002 09:45:21 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209040944120.12060-100000@localhost.localdomain> (raw)
In-Reply-To: <3D754BAE.4020402@us.ibm.com>


On Tue, 3 Sep 2002, Michael Hohnbaum wrote:

> > (NUMA systems which have tightly coupled CPUs with a smaller cache and
> > protected by a large L3 cache might benefit from sharing the runqueue as
> > well - but the target for this concept is SMT.)
> 
> Sharing a runqueue for all processors on a node of a NUMA system has the
> drawback of not accounting for cache warmth for processes. [...]

hence the 'might'.

> [...] Ideally, for a NUMA system there should continue to be individual
> runqueues per cpu (or per set of HT processors), and then a grouping of
> runqueues at the node level.  At load balancing, priority should be to
> redispatch on the same processor, followed by on the same node.  The
> pain threshold for crossing the node boundary will vary depending on the
> NUMA-ness of the hardware, so it would be good to account for this in
> the scheduler.

agreed.

	Ingo


  reply	other threads:[~2002-09-04  7:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27  1:44 Ingo Molnar
2002-08-28  6:32 ` Rusty Russell
2002-08-28 17:16   ` Ingo Molnar
2002-08-29  1:28     ` Rusty Russell
2002-09-01  1:48 ` Rusty Russell
2002-09-03 23:54 ` Michael Hohnbaum
2002-09-04  7:45   ` Ingo Molnar [this message]
2002-12-17 17:27 Walton, Shane

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=Pine.LNX.4.44.0209040944120.12060-100000@localhost.localdomain \
    --to=mingo@elte.hu \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®