> On Oct 17, 2014, at 10:23 AM, Gus Correa wrote:
>
> Hi Ralph
>
> Thank you.
> Your fixes covered much more than I could find.
> The section about the three levels of process placement
> (" Mapping, Ranking, and Binding: Oh My!") really helps.
> I would just add at the very beginning
> short s
Hi Ralph
Thank you.
Your fixes covered much more than I could find.
The section about the three levels of process placement
(" Mapping, Ranking, and Binding: Oh My!") really helps.
I would just add at the very beginning
short sentences quickly characterizing each of the three levels.
Kind of an "
I know this commit could be a little hard to parse, but I have updated the
mpirun man page on the trunk and will port the change over to the 1.8 series
tomorrow. FWIW, I’ve provided the link to the commit below so you can “preview”
it.
https://github.com/open-mpi/ompi/commit/f9d620e3a772cdeddd4
On Oct 16, 2014, at 9:43 AM, Gus Correa wrote:
> Hi Ralph
>
> Yes, I know the process placement features are powerful.
> They were already very good in 1.6, even in 1.4,
> and I just tried the new 1.8
> "-map-by l2cache" (works nicely on Opteron 6300).
>
> Unfortunately I couldn't keep track,
Hi Ralph
Yes, I know the process placement features are powerful.
They were already very good in 1.6, even in 1.4,
and I just tried the new 1.8
"-map-by l2cache" (works nicely on Opteron 6300).
Unfortunately I couldn't keep track, test, and use the 1.7 series.
I did that in the previous "odd/new
On Oct 15, 2014, at 11:46 AM, Gus Correa wrote:
> Thank you Ralph and Jeff for the help!
>
> Glad to hear the segmentation fault is reproducible and will be fixed.
>
> In any case, one can just avoid the old parameter name
> (rmaps_base_schedule_policy),
> and use instead the new parameter nam
Thank you Ralph and Jeff for the help!
Glad to hear the segmentation fault is reproducible and will be fixed.
In any case, one can just avoid the old parameter name
(rmaps_base_schedule_policy),
and use instead the new parameter name
(rmaps_base_mapping_policy)
without any problem in OMPI 1.8.3.
We talked off-list -- fixed this on master and just filed
https://github.com/open-mpi/ompi-release/pull/33 to get this into the v1.8
branch.
On Oct 14, 2014, at 7:39 PM, Ralph Castain wrote:
>
> On Oct 14, 2014, at 5:32 PM, Gus Correa wrote:
>
>> Dear Open MPI fans and experts
>>
>> This
On Oct 14, 2014, at 5:32 PM, Gus Correa wrote:
> Dear Open MPI fans and experts
>
> This is just a note in case other people run into the same problem.
>
> I just built Open MPI 1.8.3.
> As usual I put my old settings on openmpi-mca-params.conf,
> with no further thinking.
> Then I compiled th
Dear Open MPI fans and experts
This is just a note in case other people run into the same problem.
I just built Open MPI 1.8.3.
As usual I put my old settings on openmpi-mca-params.conf,
with no further thinking.
Then I compiled the connectivity_c.c program and tried
to run it with mpiexec.
That
10 matches
Mail list logo