Project

General

Profile

Bug #872

smp standalone inconsistency

Added by Jim Phillips over 3 years ago. Updated about 1 year ago.

Status:
Merged
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
10/27/2015
Due date:
% Done:

0%

Tags:

Description

If you run netlrts-smp standalone (without charmrun) +p determines the number of worker threads and +ppn is silently ignored.
For mpi-smp standalone (without mpiexec) +ppn determines the number of worker threads and +p is silently ignored.
For net-ibverbs-smp standalone either +p or +ppn are accepted, with +ppn taking precedence if both are present.


Related issues

Related to Charm++ - Bug #900: multicore eats and ignores +ppn/++ppn Merged 11/30/2015

History

#1 Updated by Nikhil Jain over 3 years ago

  • Assignee set to Eric Bohm

Assigning to Eric since he is currently tasked to resolve all such inconsistencies.

#2 Updated by Nikhil Jain over 3 years ago

  • Assignee changed from Eric Bohm to Juan Galvez

#3 Updated by Jim Phillips almost 3 years ago

Ping.

#4 Updated by Juan Galvez almost 3 years ago

The hwloc changes being worked on at Charmworks will presumably address these and other issues (if I'm not mistaken).

#5 Updated by Sam White over 1 year ago

  • Assignee changed from Juan Galvez to Evan Ramos

#6 Updated by Evan Ramos over 1 year ago

What is the desired behavior?

#7 Updated by Jim Phillips over 1 year ago

+ppn N, no +p -> N worker threads
+p N, no +ppn -> N worker threads
+ppn N +p N -> N worker threads
+ppn N +p M, M != N -> error
no +p or +ppn -> 1 worker thread

#8 Updated by Evan Ramos over 1 year ago

  • Status changed from New to Implemented

#9 Updated by Phil Miller over 1 year ago

  • Target version set to 6.9.0

#10 Updated by Evan Ramos over 1 year ago

  • Status changed from Implemented to Merged

#11 Updated by Evan Ramos about 1 year ago

  • Tags set to provisioning

Also available in: Atom PDF