Ralph filed https://svn.open-mpi.org/trac/ompi/ticket/3075 about this.
I just reviewed Brice's patch and it looks good to me (it looks like I forgot
to update the logical/physical conversion in the module_set/get methods).
Thanks!
On Apr 12, 2012, at 1:46 AM, Brice Goglin wrote:
> Hello Tetsu
Hello Tetsuya,
I think it's expected that the displayed cpusets are different.
I only converted the code that applies/retrieves the binding, I did not
touch the code that prints it.
Good to know it works.
Brice
Le 12/04/2012 05:24, tmish...@jcity.maeda.co.jp a écrit :
> Hi, Brice.
>
> Thank you
Hi, Brice.
Thank you for sending me a patch. Now, I quickly tested your try2.patch.
Then, regarding execution speed it works well.
But, in terms of core binding reports, it's still different from
openmpi-1.5.4.
I'm not sure which is better for a standard user like me, reporting logical
indexes or
Ouch - finally figured out what happened. Jeff and I did indeed address this
problem a few weeks ago. There were some changes required in a couple of places
to make it all work, so we did the work in a Mercurial branch Jeff set up.
Unfortunately, I think he got distracted by the MPI Forum shortl
Interesting. Jeff and I had discussed that very problem not that long ago, and
I could swear he fixed it - but I don't see the CMR for that code. He's on
vacation this week, so I'll wait for his return to look at it.
Thanks!
Ralph
On Apr 11, 2012, at 2:36 AM, Brice Goglin wrote:
> A quick look
Here's a better patch. Still only compile tested :)
Brice
Le 11/04/2012 10:36, Brice Goglin a écrit :
> A quick look at the code seems to confirm my feeling. get/set_module()
> callbacks manipulate arrays of logical indexes, and they do not convert
> them back to physical indexes before binding.
A quick look at the code seems to confirm my feeling. get/set_module()
callbacks manipulate arrays of logical indexes, and they do not convert
them back to physical indexes before binding.
Here's a quick patch that may help. Only compile tested...
Brice
Le 11/04/2012 09:49, Brice Goglin a écri
Le 11/04/2012 09:06, tmish...@jcity.maeda.co.jp a écrit :
> Hi, Brice.
>
> I installed the latest hwloc-1.4.1.
> Here is the output of lstopo -p.
>
> [root@node03 bin]# ./lstopo -p
> Machine (126GB)
> Socket P#0 (32GB)
> NUMANode P#0 (16GB) + L3 (5118KB)
> L2 (512KB) + L1 (64KB) + Core
Hi, Brice.
I installed the latest hwloc-1.4.1.
Here is the output of lstopo -p.
[root@node03 bin]# ./lstopo -p
Machine (126GB)
Socket P#0 (32GB)
NUMANode P#0 (16GB) + L3 (5118KB)
L2 (512KB) + L1 (64KB) + Core P#0 + PU P#0
L2 (512KB) + L1 (64KB) + Core P#1 + PU P#4
L2 (512K
Can you send the output of lstopo -p ? (you'll have to install hwloc)
Brice
tmish...@jcity.maeda.co.jp a écrit :
Hi,
I updated openmpi from version 1.5.4 to 1.5.5.
Then, an execution speed of my application becomes quite slower than
before,
due to wrong core bindings. As far as I checked, it s
Hi,
I updated openmpi from version 1.5.4 to 1.5.5.
Then, an execution speed of my application becomes quite slower than
before,
due to wrong core bindings. As far as I checked, it seems that
openmpi-1.5.4
gives correct core bindings for my magnycore based machine.
1) my script is as follows:
exp
11 matches
Mail list logo
