public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Theurer <habanero@us.ibm.com>
Subject: Re: [PATCH] (0/3) NUMA aware scheduler
Date: Thu, 16 Jan 2003 14:36:02 -0800	[thread overview]
Message-ID: <125260000.1042756562@flay> (raw)
In-Reply-To: <Pine.LNX.4.44.0301161225260.1175-100000@penguin.transmeta.com>

> Applied. 

Thank you!
 
> I also have to say that I hope this means that the HT-specific scheduler 
> stuff will go away. HT _should_ be just another NuMA issue, and right now 
> the two seem to be just slightly different ways of covering the same 
> needs.

Yup, Andrew Theurer from our performance team has been working on this.
Initial results look encouraging.

> However, I'm going away for two weeks starting tomorrow, so even if there 
> is some experimental HT/NUMA patch, I don't want it at this point. The 
> NUMA scheduler merge is more of a "get the infrastructure in place" thing 
> for me right now.

Absolutely. Hopefully by the time you return we'll have a structure for
hyperthreading in place that's reasonably tuned ;-)

There's some more tuning and tweaking we could do to the NUMA machines as
well (I'm looking at how to implement Ingo's feedback), but I'm convinced
the infrastructure is correct.

Thanks,

M.


      reply	other threads:[~2003-01-16 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 18:27 [PATCH] (0/3) NUMA aware scheduler Martin J. Bligh
2003-01-16 19:32 ` Martin J. Bligh
2003-01-16 19:48 ` Andrew Theurer
2003-01-19 22:04   ` Pavel Machek
2003-01-16 20:28 ` Linus Torvalds
2003-01-16 22:36   ` Martin J. Bligh [this message]

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=125260000.1042756562@flay \
    --to=mbligh@aracnet.com \
    --cc=habanero@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