Open jameshcorbett opened 2 years ago
Just to clarify, by "shell tasks" you mean the user tasks that the job shell launches, not the job shell itself correct?
Yeah, sorry. I was looking for the word and didn't want to say "MPI rank". I should have just said "task" since that's the standard Flux terminology.
According to David Gloe at HPE, the cpus_per_pe member of the
pals_cmd_t
struct should be "the number of Linux CPUs (hyperthreads) each PE [i.e. shell task] is bound to." He also noted thatThe value the flux-coral2 shell plugin provides is not correct because it uses the notion of hwloc cores, not Linux CPUs, and it does account for overlap.
@grondo noted that
Thankfully it seems that an improper value (e.g. 0) for the
cpus_per_pe
entry does not cause any errors, and David Gloe guessed that the value isn't read anywhere. So we can punt on the issue for a little while.