Hi,
I think orte/ompi-mca foward number of environment variables (ie:- $OMPI_*)
to its ranks. So I believe you may use $OMPI_COMM_WORLD_LOCAL_RANK to
specifically filter out parameters within the script.
Regards
Udayanga Wickramasinghe
Research Assistant
School of Informatics and Computing
Hi all,
I have a custom MPI_Op function which I use within a non blocking version
of all_reduce(). When executing the mpi program I am seeing a segfault
thrown from libNBC. It seems like this is a known issue in openMPI atleast
[1]. Is this somehow fixed in a later release version of openmpi ? I am
will need to update to 1.10 to get the
> fix.
>
> -Nathan
>
> On Wed, Dec 16, 2015 at 02:48:45PM -0500, Udayanga Wickramasinghe wrote:
> >Hi all,
> >I have a custom MPI_Op function which I use within a non blocking
> version
> >of all_reduce(). When exe
Hi devs,
I am using THREAD_MULTIPLE in openmpi version 1.8.4. However I occasionally
see following warning and my application gets hanged up intermittently.
Does this mean thread multiple mode is not supported in 1.8.4 ? Or does
openmpi has a version that fully supports this ?
opal_libevent2021_ev
Hi,
I upgraded my open-mpi version to 4.00 on a Cray Aries cluster (GNI/uGNI).
Every time I run mpi, I get the following warning. Is there any way to
suppress this message? I am not seeing this in 3.1.3 version of open-mpi.
Any idea why openfabrics device is getting initialized when cray GNI
trans
Hi,
I upgraded my open-mpi version to 4.00 on a Cray Aries cluster (GNI/uGNI).
Every time I run mpi, I get the following warning. Is there any way to
suppress this message? I am not seeing this in 3.1.3 version of open-mpi.
Any idea why openfabrics device is getting initialized when cray GNI
trans
=lau_email&utm_medium=email&utm_campaign=EmailSig2018>
>
> f <https://www.facebook.com/LebaneseAmericanUniversity>
>
> in <https://www.linkedin.com/edu/school?id=14810>
>
> t <https://twitter.com/lebamuniv>
>
> ig <https://instagram.com/lebamer
gt;
>
> On Mon, Jan 7, 2019 at 8:16 AM Udayanga Wickramasinghe
> wrote:
> >
> > Hi Salim,
> > Thank you. Yeah, I noticed warnings would vanish by turning on
> btl_openib_allow_ib -- but since this is quite annoying I am wondering if
> there is any other way to suppre
Hi,
I am running into an issue in open-mpi where it crashes abruptly
during MPI_WIN_ATTACH.
[nid00307:25463] *** An error occurred in MPI_Win_attach
[nid00307:25463] *** reported by process [140736284524545,140728898420736]
[nid00307:25463] *** on win rdma window 3
[nid00307:25463] *** MPI_ERR_
Sorry should be corrected as MPI3.0 spec [1]
[1] https://www.mpi-forum.org/docs/mpi-3.0/mpi30-report.pdf ; page=443
Best Regards,
Udayanga
On Tue, Jan 8, 2019 at 11:36 PM Udayanga Wickramasinghe
wrote:
> Hi,
> I am running into an issue in open-mpi where it crashes abruptly
&g
imit). It is
> recommended to keep the total number as small as possible.
>
> -Nathan
>
> > On Jan 8, 2019, at 9:36 PM, Udayanga Wickramasinghe
> wrote:
> >
> > Hi,
> > I am running into an issue in open-mpi where it crashes abruptly during
> MPI
ting-mca-params
>
>
>
> > On Jan 9, 2019, at 1:18 PM, Udayanga Wickramasinghe
> wrote:
> >
> > Thanks. Yes, I am aware of that however, I currently have a requirement
> to increase the default.
> >
> > Best,
> > Udayanga
> >
> > On Wed, Jan
ble either by setting:
>>
>> Environment:
>>
>> OMPI_MCA_osc_rdma_max_attach
>>
>>
>> mpirun command line:
>>
>> —mca osc_rdma_max_attach
>>
>>
>> Keep in mind that each attachment may use an underlying hardware resource
>> th
13 matches
Mail list logo