From: Cliff Wickman <cpw@sgi.com>
To: Kazunori Asayama <asayama@sm.sony.co.jp>
Cc: linux-numa@vger.kernel.org
Subject: Re: Unexpected warning on non-NUMA host
Date: Fri, 9 Jan 2009 09:15:36 -0600 [thread overview]
Message-ID: <20090109151536.GA8939@sgi.com> (raw)
In-Reply-To: <496741AD.7020006@sm.sony.co.jp>
Asayama,
On Fri, Jan 09, 2009 at 09:23:09PM +0900, Kazunori Asayama wrote:
> Hi all,
>
> When I ran a program which was linked with libnuma (version 2.0.2) but
> without libnuma function calls on non-NUMA platform, I got an unexpected
> warning message:
>
> > libnuma: Warning: /sys not mounted or no numa system. Assuming one
> node: No such file or directory
>
> I'd like to create single program which works on both of NUMA and
> non-NUMA platforms, by switching behavior according to the result of
> numa_available(). So I expect the message above isn't displayed if no
> NUMA library function except numa_available() is called, even if the
> program is linked with libnuma.
>
> AFAIK, the version 1 didn't show such message until a NUMA function
> except numa_available() was called.
>
> So is the current behavior unexpected?
libnuma's initialization attempts determine the size of everything
(configured nodes, nodemask size, max cpus, configured cpus, cpu
and node constraints of the current thread)
In doing so, it emits the warning you see if it cannot open
/sys/devices/system/node.
It sets maxconfigurednode = 0
Perhaps it shouldn't complain, but just go on quietly to avoid
the noise on a non-NUMA platform.
Any objection?
-Cliff
--
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824
next prev parent reply other threads:[~2009-01-09 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 12:23 Unexpected warning on non-NUMA host Kazunori Asayama
2009-01-09 15:15 ` Cliff Wickman [this message]
2009-01-13 1:57 ` Kazunori Asayama
2009-01-14 14:23 ` Cliff Wickman
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=20090109151536.GA8939@sgi.com \
--to=cpw@sgi.com \
--cc=asayama@sm.sony.co.jp \
--cc=linux-numa@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 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.