Project

General

Profile

Feature #1039

Feature #1173: Automatic process launching, thread spawning, and hardware binding

reject pemap/commap with duplicate or too few cpus

Added by Jim Phillips over 2 years ago. Updated 29 days ago.

Status:
New
Priority:
Low
Assignee:
Category:
Machine Layers
Target version:
-
Start date:
Due date:
% Done:

0%

Tags:

Description

Running, e.g., "+p16 +pemap 1-15" or "+pemap 0-4,4-8" is almost certainly an error and should be rejected.

History

#1 Updated by Eric Bohm over 1 year ago

  • Parent task set to #1173
  • Start date deleted (04/18/2016)
  • Target version changed from 6.8.0 to 6.8.1

Validation of the old command lines should be reconsidered when the binding substrate changes to hwloc.

#2 Updated by Sam White 11 months ago

  • Target version changed from 6.8.1 to 6.9.0

#3 Updated by Eric Bohm 9 months ago

  • Assignee set to Evan Ramos

#4 Updated by Evan Ramos 6 months ago

The function responsible for parsing these parameters, search_pemap, is not amenable to quickly adding checks for these conditions.

#5 Updated by Evan Ramos 6 months ago

  • Status changed from New to Feedback

#6 Updated by Sam White 6 months ago

I'd say we can close this issue or push it off to a future release. The new ++oneWthPer* routines should obviate the need for pemaps and commaps for most users

#7 Updated by Evan Ramos 6 months ago

  • Target version deleted (6.9.0)

#8 Updated by Evan Ramos 6 months ago

  • Status changed from Feedback to New

#9 Updated by Sam White 6 months ago

  • Priority changed from Normal to Low

#10 Updated by Evan Ramos 29 days ago

  • Tags set to provisioning

Also available in: Atom PDF