Opened 9 years ago

Last modified 5 years ago

#933 new feature

NO_LOCAL and ODD_EVEN_CLIQUES should be handled by hydra

Reported by: buntinas Owned by:
Priority: major Milestone: future
Component: mpich Keywords:

Description (last modified by balaji)

The no_local and odd_even configure flags and environment vars were used by nemesis when determining local and remote processes to treat certain processes as remote so that the network would be used for communication. With PMI 1.1 and PMI 2, the process manager determines which processes are remote vs local, so no_local and odd_even should now be options to the process manager.

Change History (5)

comment:1 Changed 9 years ago by balaji

I'm not sure this is the right solution. If we did this, for process managers that didn't support PMI-1.1 or PMI-2, you'd never use shared memory? I don't see any reason to duplicate this functionality in the MPICH2 stack and the process manager.

comment:2 Changed 8 years ago by thakur

  • Milestone changed from mpich2-1.3 to mpich2-1.3.1
  • Owner set to balaji
  • Status changed from new to assigned

comment:3 Changed 8 years ago by balaji

  • Milestone changed from mpich2-1.3.2 to future
  • Type changed from bug to feature

This is not critical, and I'm not even certain what the value add for this is, given that it's already handled within MPICH2. Kicking it off to future.

comment:4 Changed 8 years ago by buntinas

I think the idea was that since hydra is giving the node mapping this would be the right place to do this. Currently, I think the odd-even cliques is not exactly divided by odd and even processes. I agree that it's not critical, but it's something we should do eventually.

comment:5 Changed 5 years ago by balaji

  • Description modified (diff)
  • Owner balaji deleted
  • Status changed from assigned to new
Note: See TracTickets for help on using tickets.