<div dir="ltr">I think this is a question about what it means for an implementation to "ignore" an info hint. In this example, what if "foo = bar" was "invert_all_bits = true". It would probably be bad if the library returned that info key without actually doing what the user requested.<div><br></div><div> ~Jim.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 18, 2021 at 12:12 PM Raffenetti, Ken via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org">mpi-forum@lists.mpi-forum.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Here's an example program that illustrates the current file info behavior with MPICH and Open MPI. Neither library will abort the application in my tests. MPICH does not recognize the "foo" key, and I would guess the same for Open MPI.<br>
<br>
So is this correct behavior according to the standard? Or a bug? There are users who prefer the current behavior, I suspect in part because there is no attribute caching interface for MPI file objects.<br>
<br>
#include <mpi.h><br>
#include <stdlib.h><br>
#include <stdio.h><br>
#include <string.h><br>
<br>
int main(void) {<br>
MPI_Init(NULL, NULL);<br>
<br>
MPI_Info info;<br>
MPI_Info_create(&info);<br>
MPI_Info_set(info, "foo", "bar");<br>
<br>
MPI_File fh;<br>
MPI_File_open(MPI_COMM_SELF, "testfile", MPI_MODE_RDWR | MPI_MODE_CREATE, info, &fh);<br>
<br>
MPI_Info info_used;<br>
MPI_File_get_info(fh, &info_used);<br>
<br>
char value[4] = "";<br>
int flag;<br>
MPI_Info_get(info_used, "foo", 3, value, &flag);<br>
<br>
if (!flag) {<br>
printf("key not found\n");<br>
MPI_Abort(MPI_COMM_WORLD, 1);<br>
}<br>
<br>
if (strcmp(value, "bar")) {<br>
printf("value does not match\n");<br>
MPI_Abort(MPI_COMM_WORLD, 1);<br>
}<br>
<br>
MPI_File_close(&fh);<br>
MPI_Info_free(&info);<br>
MPI_Info_free(&info_used);<br>
<br>
MPI_Finalize();<br>
return 0;<br>
}<br>
<br>
On 10/15/21, 2:47 PM, "mpi-forum on behalf of Raffenetti, Ken via mpi-forum" <<a href="mailto:mpi-forum-bounces@lists.mpi-forum.org" target="_blank">mpi-forum-bounces@lists.mpi-forum.org</a> on behalf of <a href="mailto:mpi-forum@lists.mpi-forum.org" target="_blank">mpi-forum@lists.mpi-forum.org</a>> wrote:<br>
<br>
We brought this to the forum because during our internal discussion is was shown that ROMIO will return any "ignored" key/value pairs set by the user in MPI_FILE_GET_INFO. Essentially, ROMIO duplicates the users info object, and only adjusts settings for keys it recognizes. Perhaps this is wrong behavior according to MPI-4.0?<br>
<br>
This behavior was introduced into ROMIO somewhat recently in May 2020. There was a user request for it based on how OMPI-IO behaved. <a href="https://github.com/pmodels/mpich/pull/3954" rel="noreferrer" target="_blank">https://github.com/pmodels/mpich/pull/3954</a><br>
<br>
Ken<br>
<br>
On 10/13/21, 3:46 PM, "mpi-forum on behalf of Jim Dinan via mpi-forum" <<a href="mailto:mpi-forum-bounces@lists.mpi-forum.org" target="_blank">mpi-forum-bounces@lists.mpi-forum.org</a> on behalf of <a href="mailto:mpi-forum@lists.mpi-forum.org" target="_blank">mpi-forum@lists.mpi-forum.org</a>> wrote:<br>
<br>
Hi Rob,<br>
This seems reasonable to me. I think you can draw an analogy to an application setting "mpi_assert_no_any_tag = true" and checking the value returned by MPI_Comm_get_info to decide whether to use MPI_ANY_TAG on the communicator. I would suggest info values like "true" and "false" so that ROMIO can return back the same value passed by the user if the info key is accepted.<br>
<br>
As of MPI 4.0, MPI_File_get_info must return "all hints that are supported by the implementation and have default values specified; any user-supplied hints that were not ignored by the implementation; and any additional hints that were set by the implementation." So, true/false would also allow ROMIO to return a default value for the info key if the user hasn't set it.<br>
<br>
One thing you can't do with info today is fail the operation because of a key/value pair in the info argument. If there is an issue with a particular key/value pair, it is supposed to be ignored.<br>
<br>
~Jim.<br>
<br>
<br>
On Mon, Oct 11, 2021 at 2:13 PM Latham, Robert J. via mpi-forum <<a href="mailto:mpi-forum@lists.mpi-forum.org" target="_blank">mpi-forum@lists.mpi-forum.org</a>> wrote:<br>
<br>
<br>
I'd like a way to tell users programmatically about features ROMIO supports.<br>
<br>
One way I imagined doing so was through the info object, though we're having some internal discussion about how kosher that is. Any thoughts from the broader MPI community about an approach like this:<br>
<br>
<br>
```<br>
MPI_Info_create(&info);<br>
MPI_Info_set(info, "romio_feature_xyz", "requested");<br>
MPI_File_open(...)<br>
MPI_File_get_info(fh, &info_used)<br>
MPI_File_get_info(info_used, "romio_feature_xyz", MPI_MAX_INFO_VAL-1,<br>
value, &flag);<br>
<br>
```<br>
<br>
Possible points of contention:<br>
<br>
- we have examples of using hints for clients to pass information to implementations (striping_factor, cb_buffer_size) and examples of implementations passing information to users (cb_nodes on Blue Gene), but we don't have too many examples of two-way hints.<br>
<br>
- will MPI_File_get_info return all info keys or just the ones the implementation understands? The standard dictates what is required to be returned. ROMIO (so de facto standard) will return the union of its internal keys and any keys (known or unknown) passed in by the user.<br>
<br>
- The use of "requested" as a hint value that the implementation can then either set to "enabled" or "disabled" guards the situation where a user code is passing these infos to an older MPI IO implementation. If the hint comes back exactly as given, then the implementation ignored this feature request and it is not supported. If the hint comes back "enabled" then the caller knows something about the implementation.<br>
<br>
Thanks<br>
==rob<br>
<br>
<br>
_______________________________________________<br>
mpi-forum mailing list<br>
<a href="mailto:mpi-forum@lists.mpi-forum.org" target="_blank">mpi-forum@lists.mpi-forum.org</a><br>
<a href="https://lists.mpi-forum.org/mailman/listinfo/mpi-forum" rel="noreferrer" target="_blank">https://lists.mpi-forum.org/mailman/listinfo/mpi-forum</a><br>
<br>
_______________________________________________<br>
mpi-forum mailing list<br>
<a href="mailto:mpi-forum@lists.mpi-forum.org" target="_blank">mpi-forum@lists.mpi-forum.org</a><br>
<a href="https://lists.mpi-forum.org/mailman/listinfo/mpi-forum" rel="noreferrer" target="_blank">https://lists.mpi-forum.org/mailman/listinfo/mpi-forum</a><br>
<br>
_______________________________________________<br>
mpi-forum mailing list<br>
<a href="mailto:mpi-forum@lists.mpi-forum.org" target="_blank">mpi-forum@lists.mpi-forum.org</a><br>
<a href="https://lists.mpi-forum.org/mailman/listinfo/mpi-forum" rel="noreferrer" target="_blank">https://lists.mpi-forum.org/mailman/listinfo/mpi-forum</a><br>
</blockquote></div>