public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Michael Hohnbaum <hohnbaum@us.ibm.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu,
	Erich Focht <efocht@ess.nec.de>
Subject: Re: [PATCH 2.5.45] NUMA Scheduler  (1/2)
Date: 31 Oct 2002 19:10:42 -0500	[thread overview]
Message-ID: <1036109447.1067.27.camel@phantasy> (raw)
In-Reply-To: <1010470000.1036108344@flay>

On Thu, 2002-10-31 at 18:52, Martin J. Bligh wrote:

> Just wanted to add that everyone that's been involved in this is
> now in harmonious agreement about this combined solution. If you're
> curious as to where the benefits come from, the differences in 
> kernel profiles are included below from a 16-way NUMA-Q doing a
> kernel compile.

Linus, although these patches are fairly straightforward and
non-impacting in the !CONFIG_NUMA case, would you prefer it if a
non-NUMA person who knew the scheduler (say, me) went over these patches
and merged them with you?

Ingo, do you have an opinion either way?  I think basic NUMA support,
especially in the load balancer, should make it in before 2.6.

	Robert Love


  reply	other threads:[~2002-11-01  0:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 23:31 [PATCH 2.5.45] NUMA Scheduler (1/2) Michael Hohnbaum
2002-10-31 23:33 ` [PATCH 2.5.45] NUMA Scheduler (2/2) Michael Hohnbaum
2002-10-31 23:52 ` [PATCH 2.5.45] NUMA Scheduler (1/2) Martin J. Bligh
2002-11-01  0:10   ` Robert Love [this message]
2002-11-01  2:35   ` Martin J. Bligh
2002-11-01 17:06   ` Erich Focht

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=1036109447.1067.27.camel@phantasy \
    --to=rml@tech9.net \
    --cc=efocht@ess.nec.de \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mingo@elte.hu \
    --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