From: Paul Jackson <pj@sgi.com>
To: Andi Kleen <ak@muc.de>
Cc: ak@muc.de, anton@samba.org, linux-kernel@vger.kernel.org,
lse-tech@projects.sourceforge.net
Subject: Re: NUMA API observations
Date: Mon, 14 Jun 2004 17:06:05 -0700 [thread overview]
Message-ID: <20040614170605.130d9a67.pj@sgi.com> (raw)
In-Reply-To: <20040614234430.GB90963@colin2.muc.de>
Andi wrote:
> I add some code to go upto a page now.
good.
> This adds a hardcoded limit of 32768 CPUs to libnuma.
Ok - SGI has no issues with a 32768 CPU limit ... for now ;).
> I really dislike this error code [EINVAL] btw ...
Then use others ??
The way I learned Unix, decades ago, the tradition was to use a variety
of errno values, even if they were a slightly strange fit, in order to
provide more detailed error feedback. Look for example at the rename(2)
or acct(2) system calls.
So long as the man page shows them, it can be helpful.
--
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 0:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 15:36 NUMA API observations 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-06-15 4:59 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
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
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=20040614170605.130d9a67.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@muc.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@projects.sourceforge.net \
/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