[mvapich-discuss] (no subject)

Nenad Vukicevic nenad at intrepid.com
Wed Feb 24 12:54:33 EST 2016


I got the same result.

[nenad at dev one-sided]$ mpirun -n 2 osu_acc_latency

WARNING: Error in initializing MVAPICH2 ptmalloc library.Continuing without
InfiniBand registration cache support.

# OSU MPI_Accumulate latency Test v5.2

# Window creation: MPI_Win_allocate

# Synchronization: MPI_Win_flush

# Size          Latency (us)

0                       0.14

1                       3.50

2                       3.12

4                       3.01

8                       3.99

16                      4.02

32                      4.04

64                      4.14

128                     4.79

256                     5.08

512                     5.50

1024                    6.42

2048                    7.51

4096                    8.93

8192                   13.53

16384                  26.76

32768                  43.19

65536                 193.44

131072                261.60

262144                397.56

524288                670.97

1048576              1214.61

2097152              2692.48

4194304              5265.03

On Wed, Feb 24, 2016 at 8:22 AM, Nenad Vukicevic <nenad at intrepid.com> wrote:

> We are not doing anything special,  the warning appears on a simple hello
> program. I have MVAPICh built from 2.2b with and without debugging, and
> also with RPM created from the RHEL 6 spec.  Note that this is fairly new
> Fedora (FC23).
>
> I'll try OMB for warnings.
>
>
> On Wed, Feb 24, 2016 at 7:28 AM, Jonathan Perkins <
> perkinjo at cse.ohio-state.edu> wrote:
>
>> Hello Nenad.  Can you tell us more about your application?  Specifically
>> if there are any libraries or special handling of memory allocation that
>> may be linked in.  This type of problem usually occurs if MVAPICH2 isn't
>> able to properly intercept the malloc and free calls.
>>
>> If you don't believe that your application is doing anything like this,
>> can you verify that you're able to run the OMB suite (such as osu_latency)
>> without this warning being emitted.
>>
>> On Wed, Feb 24, 2016 at 3:11 AM Nenad Vukicevic <nenad at intrepid.com>
>> wrote:
>>
>>> X-MS-Exchange-CrossTenant-FromEntityHeade
>>> --===============3181330637561286136==
>>> Content-Type: multipart/alternative;
>>> boundary="089e0112c5cce95adb052c794745"
>>>
>>> --089e0112c5cce95adb052c794745
>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>> We are running mvapich 2.2b on Fedora 23. We are getting the following
>>> warning when running the code:
>>>
>>> WARNING: Error in initializing MVAPICH2 ptmalloc library.Continuing
>>> without
>>> InfiniBand registration cache support.
>>>
>>> I saw some previous discussions on the subject but none of the suggested
>>> solutions worked (there was a patch on 2.1a(?), plus LD_PRELAOD of mpich
>>> library, etc..).
>>>
>>> This error shows up on a simple hello test but only if we run on multiple
>>> nodes.  I can run multiple threads on the same node without causing this
>>> warning.
>>>
>>> Any idea what we can try?  I understand that there will be a slight
>>> decrease in performance if we disable ptmalloc.
>>>
>>> --
>>> Nenad
>>>
>>> --089e0112c5cce95adb052c794745
>>> Content-Type: text/html; charset="UTF-8"
>>> Content-Transfer-Encoding: quoted-printable
>>>
>>> <div dir=3D"ltr">We are running mvapich 2.2b on Fedora 23. We are
>>> getting t=
>>> he following warning when running the code:<div>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> <p class=3D""><span class=3D"">WARNING: Error in initializing MVAPICH2
>>> ptma=
>>> lloc library.Continuing without InfiniBand registration cache
>>> support.</spa=
>>> n></p><p class=3D"">I saw some previous discussions on the subject but
>>> none=
>>>  of the suggested solutions worked (there was a patch on 2.1a(?), plus
>>> LD_P=
>>> RELAOD of mpich library, etc..).</p><p class=3D"">This error shows up on
>>> a =
>>> simple hello test but only if we run on multiple nodes.=C2=A0 I can run
>>> mul=
>>> tiple threads on the same node without causing this warning.</p><p
>>> class=3D=
>>> "">Any idea what we can try?=C2=A0 I understand that there will be a
>>> slight=
>>>  decrease in performance if we disable ptmalloc.</p><div><br></div>--
>>> <br><=
>>> div class=3D"gmail_signature"><div dir=3D"ltr"><div><div
>>> dir=3D"ltr">Nenad<=
>>> /div></div></div></div>
>>> </div></div>
>>>
>>> --089e0112c5cce95adb052c794745--
>>>
>>> --===============3181330637561286136==
>>> Content-Type: text/plain; charset="us-ascii"
>>> MIME-Version: 1.0
>>> Content-Transfer-Encoding: 7bit
>>> Content-Disposition: inline
>>>
>>> _______________________________________________
>>> mvapich-discuss mailing list
>>> mvapich-discuss at cse.ohio-state.edu
>>> http://mailman.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
>>>
>>> --===============3181330637561286136==--
>>>
>>
>
>
> --
> Nenad
>



-- 
Nenad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20160224/66dd6517/attachment-0001.html>


More information about the mvapich-discuss mailing list