Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More fine-grained MPI Details control #18

Open
ompiteam opened this issue Sep 13, 2014 · 1 comment
Open

More fine-grained MPI Details control #18

ompiteam opened this issue Sep 13, 2014 · 1 comment
Assignees

Comments

@ompiteam
Copy link
Contributor

The current MPI details scheme might not be flexible enough for all scenarios. Here's one scenario that it does not do well. It's not an urgent problem, but it might be good to make MPI details be fleible enough to handle this kind of scenario:

  • cluster of 32 4-way SMPs
  • want to test several BTLs, including "sm"
  • but "sm" cannot be tested by itself except when we are running one one node

For example, the following MPI details definition, when spanning multiple nodes, will not work because multi-node jobs will be launched with "--mca btl self,sm":

{{{
[MPI Details: Open MPI]
exec = mpirun -np &test_np() --prefix &test_prefix() --mca btl self,@btl@ &test_executable() &test_argv()
btl = &enumerate("tcp", "sm")
}}}

Instead, it seems like we want to make the value of @btl@ be a bit more conditional -- in this case, we want it to be dependent upon how many nodes (''not'' the value of np!) the job will run across.

@ompiteam ompiteam self-assigned this Sep 13, 2014
@ompiteam ompiteam added this to the Future milestone Sep 13, 2014
@ompiteam ompiteam added the bug label Sep 13, 2014
@ompiteam
Copy link
Contributor Author

Imported from trac issue 17. Created by jsquyres on 2006-08-24T10:21:41, last modified: 2006-12-06T11:05:33

@jjhursey jjhursey modified the milestones: Future, ArchivedFuture May 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants