From: Paul Jackson <pj@sgi.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: ak@muc.de, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net, anton@samba.org
Subject: Re: NUMA API observations
Date: Tue, 15 Jun 2004 11:32:29 -0700 [thread overview]
Message-ID: <20040615113229.054e02e2.pj@sgi.com> (raw)
In-Reply-To: <40CF33D6.80302@colorfullife.com>
Manfred wrote:
> What's the largest number of cpus that are supported right now? 256?
Kernels for SGI's SN2 boxes are usually compiled with NR_CPUS == 512.
A quick grep of the default config files shows that is the largest.
> First call sysctl or whatever. If it fails, then glibc can assume 256.
Yes, one _could_ write code such as that.
Spend a little time looking at what glibc has done so far with these
API's. You will then doubt that the code you recommend would actually
happen consistently. Be forewarned - if you are on anti-depressant
medications, make sure your prescription is filled first.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-06-15 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 4:59 NUMA API observations Manfred Spraul
2004-06-15 6:18 ` Paul Jackson
2004-06-15 11:03 ` Andi Kleen
2004-06-15 17:37 ` Manfred Spraul
2004-06-15 18:32 ` Paul Jackson [this message]
2004-06-15 18:18 ` Paul Jackson
[not found] <271SM-3DT-7@gated-at.bofh.it>
[not found] ` <27lI4-29E-19@gated-at.bofh.it>
2004-06-15 13:27 ` Andi Kleen
[not found] ` <272lY-44B-49@gated-at.bofh.it>
[not found] ` <2772a-7VK-9@gated-at.bofh.it>
[not found] ` <279nf-1id-3@gated-at.bofh.it>
2004-06-15 13:52 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2004-06-14 15:36 Anton Blanchard
2004-06-14 16:17 ` Andi Kleen
2004-06-14 21:21 ` Paul Jackson
2004-06-14 23:44 ` Andi Kleen
2004-06-15 0:06 ` Paul Jackson
2004-06-15 0:20 ` Andi Kleen
2004-06-15 0:25 ` Paul Jackson
2004-06-14 21:40 ` Anton Blanchard
2004-06-14 23:49 ` Andi Kleen
2004-06-15 13:50 ` Jesse Barnes
2004-06-15 12:53 ` Thomas Zehetbauer
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=20040615113229.054e02e2.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@muc.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=manfred@colorfullife.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.