This is expected.  Currently, the only way to not have MPICH poll is to configure with --with-device=ch3:sock.  Please note that this can cause performance loss (the polling is helpful for performance in the common case).

We are planning to allow this in the default build as well in the future.

  — Pavan

On May 8, 2014, at 7:54 AM, Anatoly G <anatolyrishon@gmail.com> wrote:

> Dear MPICH forum.
> I created an endless MPI program.
> In this program each process calls MPI_Recv from other process, w/o any MPI_Send.
> When I execute this program I see each process takes ~ 100% CPU core.
> Is this behavior (I suppose polling) is normal?
> May I reduce MPI_Recv CPU penalty?
>
> Regards,
> Anatoly.

> <mpi_polling.cpp>_______________________________________________
> discuss mailing list     discuss@mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________
discuss mailing list     discuss@mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss