Hi guys,
I faced with an issue on our cluster related to mapping & binding policies
on 1.8.5.
The matter is that --report-bindings output doesn't correspond to the
locale. It looks like there is a mistake on the output itself, because it
just puts serial core number while that core can be on anot
Ralph's the authority on this one, but just to be sure: are all nodes the same
topology? E.g., does adding "--hetero-nodes" to the mpirun command line fix the
problem?
> On Apr 20, 2015, at 9:29 AM, Elena Elkina wrote:
>
> Hi guys,
>
> I faced with an issue on our cluster related to mapping
Also, was this with HT's enabled? I'm wondering if the print code is
incorrectly computing the core because it isn't correctly accounting for HT
cpus.
On Mon, Apr 20, 2015 at 3:49 PM, Jeff Squyres (jsquyres) wrote:
> Ralph's the authority on this one, but just to be sure: are all nodes the
> sa
level of logical CPU numbering?
-Devendar
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
Sent: Monday, April 20, 2015 3:52 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] binding output error
Also, was this with HT's enabled? I'm wondering if the pri
Hi Devendar,
As far as I know, the report-bindings option shows the logical
cpu order. On the other hand, you are talking about physical one,
I guess.
Regards,
Tetsuya Mishima
2015/04/21 9:04:37、"devel"さんは「Re: [OMPI devel] binding output
error」で書きました
> HT is not enabled. All node
L#20 (256KB) + L1 L#20 (32KB) + Core L#20 + PU L#20 (P#13)
>>
>> L2 L#21 (256KB) + L1 L#21 (32KB) + Core L#21 + PU L#21 (P#21)
>>
>> L2 L#22 (256KB) + L1 L#22 (32KB) + Core L#22 + PU L#22 (P#22)
>>
>> L2 L#23 (256KB) + L1 L#23 (32KB) + Core L#23 + P
d, you are talking about physical one,
> > I guess.
> >
> > Regards,
> > Tetsuya Mishima
> >
> > 2015/04/21 9:04:37、"devel"さんは「Re: [OMPI devel] binding output
> > error」で書きました
> >> HT is not enabled. All node are same topo . This is reproducible ev
I agree.
-Original Message-
From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Jeff Squyres
(jsquyres)
Sent: Tuesday, April 21, 2015 7:17 AM
To: Open MPI Developers List
Subject: Re: [OMPI devel] binding output error
+1
Devendar, you seem to be reporting a different issue
lf Of Jeff Squyres
> (jsquyres)
> Sent: Tuesday, April 21, 2015 7:17 AM
> To: Open MPI Developers List
> Subject: Re: [OMPI devel] binding output error
>
> +1
>
> Devendar, you seem to be reporting a different issue than Elena...? FWIW:
> Open MPI has always used logi
On Apr 22, 2015, at 11:13 PM, Ralph Castain wrote:
>
> every bios does it differently, so there is no way to provide a
> standardized output. This is why we have report-bindings to tell the user
> where they actually wound up.
Maybe we should label the --display-devel-map with "P" to indicate
Thanks guys, you're right.
This is an output of lstopo on our system which confirms that logical cpus
numbering is used in report bindings:
lstopo -l
Machine (256GB)
NUMANode L#0 (P#0 128GB) + Socket L#0 + L3 L#0 (35MB)
L2 L#0 (256KB) + L1 L#0 (32KB) + Core L#0 + PU L#0 (P#0)
L2 L#1 (256
FWIW: I just pushed a change that makes the devel-map output match the
report-bindings output format so we reduce confusion.
HTH
Ralph
> On Apr 23, 2015, at 4:29 AM, Elena Elkina wrote:
>
> Thanks guys, you're right.
>
> This is an output of lstopo on our system which confirms that logical c
Awesome; I think that definitively squashes any confusion. Thanks!
> On Apr 23, 2015, at 7:31 AM, Ralph Castain wrote:
>
> FWIW: I just pushed a change that makes the devel-map output match the
> report-bindings output format so we reduce confusion.
>
> HTH
> Ralph
>
>
>> On Apr 23, 2015, a
13 matches
Mail list logo
