n Behalf Of
> *Xiaolong
> Cui
> *Sent:* Thursday, August 11, 2016 2:13 PM
>
> *To:* Open MPI Users
> *Subject:* Re: [OMPI users] runtime performance tuning for Intel OMA
> interconnect
>
>
>
> Sorry, forgot the attachments.
>
>
>
> On Thu, Aug 11, 2016
...@lists.open-mpi.org] On Behalf Of Xiaolong Cui
Sent: Thursday, August 11, 2016 2:13 PM
To: Open MPI Users
Subject: Re: [OMPI users] runtime performance tuning for Intel OMA interconnect
Sorry, forgot the attachments.
On Thu, Aug 11, 2016 at 5:06 PM, Xiaolong Cui
mailto:sunshine...@gmail.com
ESH -> Largest supported
>> value.
>>
>>
>>
>> Regards,
>>
>>
>>
>> _MAC
>>
>>
>>
>> *From:* users [mailto:users-boun...@lists.open-mpi.org] *On Behalf Of
>> *Xiaolong
>> Cui
>> *Sent:* Wednesday,
PSM2_MQ_RNDV_HFI_THRESH -> Largest supported
> value.
>
>
>
> Regards,
>
>
>
> _MAC
>
>
>
> *From:* users [mailto:users-boun...@lists.open-mpi.org] *On Behalf Of
> *Xiaolong
> Cui
> *Sent:* Wednesday, August 10, 2016 7:19 PM
> *To:* Open MPI Users
Open MPI Users
Subject: Re: [OMPI users] runtime performance tuning for Intel OMA interconnect
Hi Matias,
Thanks a lot, that's very helpful!
What I need indeed is to always use eager mode. But I didn't find any
information about PSM2_MQ_EAGER_SDMA_SZ online. Would you please elaborat
change the subject OMA -> OPA
>
>
>
>
>
> *From:* users [mailto:users-boun...@lists.open-mpi.org
> ] *On Behalf Of *Xiaolong Cui
> *Sent:* Tuesday, August 09, 2016 2:22 PM
> *To:* users@lists.open-mpi.org
> *Subject:* [OMPI users] runtime performance tuning for Intel OM
users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Xiaolong Cui
Sent: Tuesday, August 09, 2016 2:22 PM
To: users@lists.open-mpi.org<mailto:users@lists.open-mpi.org>
Subject: [OMPI users] runtime performance tuning for Intel OMA interconnect
I used to tune the performance of OpenMP
I used to tune the performance of OpenMPI on InfiniBand by changing the
OpenMPI MCA parameters for openib component (see
https://www.open-mpi.org/faq/?category=openfabrics). Now I migrate to a new
cluster that deploys Intel's omni-path interconnect, and my previous
approach does not work any more.