Fix a couple of minor issues with IOR output #493
Conversation
This commit fixes two issues: - The AIO backend prints the max outstanding transactions when starting. This is printed by every MPI rank and doesn't add much. Probably is left over from some debugging. - Init MPI ***before*** parsing the command line. Without this every rank thinks it is rank 0 so messages that should only be printed by rank 0 are printed n times. Signed-off-by: Nathan Hjelm <[email protected]>
|
Been a long time since I touched IOR but these two issues have been bugging me. Julian, PTAL. |
|
The only issue is the whole parse for -h before starting MPI thing. I can probably work around that if we want to maintain that. Honestly, starting MPI as a singleton is basically free so not a big deal. |
|
The issue with -h is that there exist some MPI implementations that require a parallel job to be started before they can be initialized. Thus, it would not be possible to see the arguments of ior without running it in a parallel job. |
This commit fixes two issues:
The AIO backend prints the max outstanding transactions when starting. This is printed by every MPI rank and doesn't add much. Probably is left over from some debugging.
Init MPI before parsing the command line. Without this every rank thinks it is rank 0 so messages that should only be printed by rank 0 are printed n times.