[mpiwg-hybridpm] mpi_memory_alloc_kinds questions/clarifications
Raffenetti, Ken
raffenet at anl.gov
Wed Jan 29 12:41:33 CST 2025
I asked about the last scenario in Slack, but the discussion is unfortunately lost. My recollection was that this sentence on pg 509, ln 26-27:
The substrings that indicate support for these memory allocation kinds must be identical to those supplied by the user.
means that you cannot _only_ return “rocm” when the request was for “rocm:device”. MPICH will return both “rocm,rocm:device” for such a request.
Ken
From: mpiwg-hybridpm <mpiwg-hybridpm-bounces at lists.mpi-forum.org> on behalf of Edgar Gabriel via mpiwg-hybridpm <mpiwg-hybridpm at lists.mpi-forum.org>
Date: Wednesday, January 29, 2025 at 11:55 AM
To: Hybrid working group mailing list <mpiwg-hybridpm at lists.mpi-forum.org>
Cc: Edgar Gabriel <edgar.gabriel1 at outlook.com>
Subject: [mpiwg-hybridpm] mpi_memory_alloc_kinds questions/clarifications
More relevant however is potentially something else. When user requests e.g. with
mpiexec -mpi-memory-alloc-kinds system,mpi,rocm:device -np 32 …
the MPI library is allowed to return more memory types than requested by the user, e.g. it would be valid for mpi_memory_alloc_kinds info to contain
mpi,system,rocm:device,rocm:host,rocm:managed
or
mpi,system,rocm
which is equivalent in my understanding, since device,host,and managed are all the memory types supported by the rocm memkind, and supporting all three of them is equivalent to not providing any restrictors. Our examples in the side document could not handle that however, what we would need to do e.g. for the rocm testcase would be something like
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-hybridpm/attachments/20250129/7f59e75a/attachment.html>
More information about the mpiwg-hybridpm
mailing list