mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	William Voorsluys <william@icmc.usp.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NPTL/SMP/NUMA
Date: Tue, 03 Jun 2003 23:11:44 -0700	[thread overview]
Message-ID: <227280000.1054707103@[10.10.2.4]> (raw)
In-Reply-To: <1054679535.9233.87.camel@dhcp22.swansea.linux.org.uk>

>> thinking on SMP machines, and which have been made to other purposes?
>> Is there any feature on the library/kernel that make it possible to
>> exploit the benefits of NUMA systems?
> 
> NUMA systems don't have any benefits (well other than engineering 
> considerations like practicality of construction). 

Personally, I'd say that's pretty important ;-) But I get your point ...

On the other hand, you could look at it as "better local latency" rather
than "worse remote latency". Particularly if you stand on a big Sun
server when you look, where everything sucks equally for memory access 
latencies ;-)

> From a software perspective NUMA is simply a question of making the 
> loss as little as possible.

 
> There are patches to do more NUMA aware scheduling which help a bit
> as well as to do things like replicate the kernel code to each node.

The NUMA scheduling code isn't very bright about threads right now,
but we will fix that soon enough ;-)

M.


      reply	other threads:[~2003-06-04  5:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 22:26 NPTL/SMP/NUMA William Voorsluys
2003-06-03 22:32 ` NPTL/SMP/NUMA Alan Cox
2003-06-04  6:11   ` 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='227280000.1054707103@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william@icmc.usp.br \
    /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®