From: Manfred Spraul <manfred@colorfullife.com>
To: Andi Kleen <ak@muc.de>
Cc: pj@sgi.com, linux-kernel@vger.kernel.org,
lse-tech <lse-tech@lists.sourceforge.net>,
Anton Blanchard <anton@samba.org>
Subject: Re: NUMA API observations
Date: Tue, 15 Jun 2004 19:37:26 +0200 [thread overview]
Message-ID: <40CF33D6.80302@colorfullife.com> (raw)
In-Reply-To: <20040615110320.GD50463@colin2.muc.de>
Andi Kleen wrote:
>Or maybe just a sysctl. But it doesn't really help because
>applications have to work with older kernels.
>
What's the largest number of cpus that are supported right now? 256?
First call sysctl or whatever. If it fails, then glibc can assume 256.
If someone installs an old kernel on a new computer then it's his own
fault. The API is broken, we should fix it now - it will only get more
painful in the future.
--
Manfred
next prev parent reply other threads:[~2004-06-15 17:39 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 [this message]
2004-06-15 18:32 ` Paul Jackson
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=40CF33D6.80302@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=ak@muc.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=pj@sgi.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