Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Development mailing list

Subject: Re: [hwloc-devel] 1.0.3rc3 and 1.1rc5
From: Guy Streeter (streeter_at_[hidden])
Date: 2010-12-20 14:06:46


On 12/20/2010 12:56 PM, Brice Goglin wrote:
> Le 20/12/2010 19:40, Guy Streeter a écrit :
>> Get this singlethreaded process memory : expected 0x0000000f, got
>> 0xf...f
>>
>> Is that a bug?
>> That's on my Fedora 13 non-numa system.
>
> This is kind of expected. 0x0000000f means all the cores in the machine.
> 0xf...f means all the machine when the machine isn't numa. It's hard to
> make things strictly the same without loosing some semantics and keeping
> things simple. Fortunately, your application won't see any actual
> difference unless it actually compares full cpusets like above.
>
>> On my RHEL6.0 numa system,
>>
>> Get this singlethreaded process memory : expected 0x00ffffff, got
>> 0x0000003f
>
> In which section of hwloc_bind is this? Sometimes, the difference is
> normal too because Linux doesn't exactly do what we want.
>
> Brice
>
> _______________________________________________
> hwloc-devel mailing list
> hwloc-devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel

I decided I should just give you the whole output.
--Guy