Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-devel] More memory binding questions
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2011-01-06 10:19:15

Perfect; thanks! Commit coming shortly.

On Jan 6, 2011, at 1:56 AM, Samuel Thibault wrote:

> Jeff Squyres, le Thu 06 Jan 2011 03:39:28 +0100, a écrit :
>> * \note HWLOC_MEMBIND_STRICT is only supported with this function on
>> * some systems. If it is specified on an unsupported system, -1 is
>> * returned and errno is set to ENOSYS.
> Err, not exactly: there is currently no system where hwloc_get_membind
> is supported without STRICT but not supported with STRICT.
>> * If HWLOC_MEMBIND_STRICT is not specified, or if all the process'
>> * (or thread's) pages have the same memory binding policy,
> policy _and nodeset_ (i.e. actually just one node).
>> \p nodeset
>> * is cleared. Each page is then examined and has the bit set in \p
>> * nodeset corresponding to the NUMA node where it is located. The
>> * resulting \p nodeset represents the set of NUMA nodes containing
>> * all the pages in the process (or thread).
> Samudl
> _______________________________________________
> hwloc-devel mailing list
> hwloc-devel_at_[hidden]

Jeff Squyres
For corporate legal information go to: