From: Cliff Wickman <cpw@sgi.com>
To: "Amit K. Arora" <aarora@linux.vnet.ibm.com>
Cc: linux-numa@vger.kernel.org
Subject: Re: [PATCH 0/2] non-contiguous NUMA nodes handling in numactl and libnuma
Date: Mon, 2 Mar 2009 07:58:36 -0600 [thread overview]
Message-ID: <20090302135836.GB1587@sgi.com> (raw)
In-Reply-To: <20090302130546.GA31167@amitarora.in.ibm.com>
Hi Amit,
Thanks much for the patches.
I tested them this morning. The standard tests pass on ia64 (8 nodes).
The patches are included in the numactl-2.0.3-rc2.tar.gz tarball at
ftp://oss.sgi.com/www/projects/libnuma/download/
Any other review and testing is welcome.
-Cliff
On Mon, Mar 02, 2009 at 06:35:46PM +0530, Amit K. Arora wrote:
> PROBLEM: If the NUMA nodes in a system are not contiguous, numactl shows
> incorrect output. Here is an example from one such system:
>
> ------------------------------------------------------
> # ls /sys/devices/system/node
> has_cpu has_normal_memory node0 node1 node4 node5 online possible
> # numactl --hardware
> available: 6 nodes (0-5)
> node 0 cpus: 0 1 2 3
> node 0 size: 15232 MB
> node 0 free: 2265 MB
> node 1 cpus: 4 5 6 7
> node 1 size: 16256 MB
> node 1 free: 3108 MB
> libnuma: Warning: /sys not mounted or invalid. Assuming one node: No
> such file or directory
> node 2 cpus:
> node 2 size: <not available>
> node 2 free: <not available>
> node 3 cpus:
> node 3 size: <not available>
> node 3 free: <not available>
> node 4 cpus: 8 9 10 11
> node 4 size: 16000 MB
> node 4 free: 9292 MB
> node 5 cpus: 12 13 14 15
> node 5 size: 16128 MB
> node 5 free: 9479 MB
> node distances:
> node 0 1 2 3 4 5
> 0: 10 20 20 20 20 10
> 1: 20 10 20 20 0 0
> 2: 0 0 0 0 0 0
> 3: 0 0 0 0 0 0
> 4: 0 0 0 1112145 1024 2607344
> 5: 1024 2607344 1024 2607344 0 0
> ------------------------------------------------------
>
>
> As we see above, there are three problems with above output:
> o it is showing wrong number of available nodes
> Actually there are 4 nodes available, but it says "6".
> o it tries to access information for non-exsistent nodes from /sys
> Thus displaying a wrong warning message too
> o the NUMA distances it shows above are clearly incorrect.
>
> Following two patches fixes these problems:
> 1) numactl-handle-NUMA-dist-properly.patch
> 2) numactl-ignore-nonavailable-nodes.patch
>
>
> --
> Regards,
> Amit Arora
> --
> To unsubscribe from this list: send the line "unsubscribe linux-numa" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824
next prev parent reply other threads:[~2009-03-02 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 13:05 [PATCH 0/2] non-contiguous NUMA nodes handling in numactl and libnuma Amit K. Arora
2009-03-02 13:19 ` [PATCH 1/2] handle NUMA distances properly for non-contiguous nodes Amit K. Arora
2009-03-02 13:23 ` [PATCH 2/2] ignore unavailable NUMA nodes Amit K. Arora
2009-03-02 13:27 ` Results after applying the patch Amit K. Arora
2009-03-02 13:58 ` Cliff Wickman [this message]
2009-03-09 13:17 ` [PATCH] distance table for non-contiguous NUMA nodes Amit K. Arora
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=20090302135836.GB1587@sgi.com \
--to=cpw@sgi.com \
--cc=aarora@linux.vnet.ibm.com \
--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.