From: Bill Davidsen <davidsen@tmr.com>
To: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: NUMA API observations
Date: Tue, 15 Jun 2004 09:52:30 -0400 [thread overview]
Message-ID: <40CEFF1E.70201@tmr.com> (raw)
In-Reply-To: <279nf-1id-3@gated-at.bofh.it>
Andi Kleen wrote:
> On Mon, Jun 14, 2004 at 02:21:28PM -0700, Paul Jackson wrote:
>
>>Andi wrote:
>>
>>>How should a user space application sanely discover the cpumask_t
>>>size needed by the kernel? Whoever designed that was on crack.
>>>
>>>I will probably make it loop and double the buffer until EINVAL
>>>ends or it passes a page and add a nasty comment.
>>
>>I agree that a loop is needed. And yes someone didn't do a very
>>good job of designing this interface.
>
>
> I add some code to go upto a page now.
>
> This adds a hardcoded limit of 32768 CPUs to libnuma. That's not
> nice, but we have to stop somewhere in case the EINVAL is returned
> for other reason
Should be enough for desktop machines...
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-06-15 13:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <271SM-3DT-7@gated-at.bofh.it>
[not found] ` <27lI4-29E-19@gated-at.bofh.it>
2004-06-15 13:27 ` NUMA API observations 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 [this message]
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
-- 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=40CEFF1E.70201@tmr.com \
--to=davidsen@tmr.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/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