On Mon, Feb 25, 2013 at 7:55 AM, Pavan Balaji <balaji@mcs.anl.gov> wrote:

On 02/23/2013 06:49 PM US Central Time, Jeff Hammond wrote:
> My understanding, having looked at the code for this, is that no
> thread binding is set. The OS will hopefully do the right thing when
> the cores are undersubscribed, but I see no thread affinity code in
> the MPICH source for the comm threads.

This is incorrect. Hydra allows you to bind a process to a cpuset. If
you are using an affinity thread, make sure your cpuset has at least 2
cores in it.

It sounds like you are binding a process. Suppose hydra binds my process to cpuset 0xf and my process pthread_creates a total of three threads. If I bind those threads to 0x1, 0x2, 0x4, we still have the MPICH_ASYNC_PROGRESS running with affinity 0xf, and as far as I know, there is no way to bind it to 0x8.

It would be interesting to be able to specify this, both to place the progress threads close to NICs and to make sure that progress threads do not disrupt application threads (to reduce jitter and possibly improve performance).