1
1
openmpi/ompi/mca/io
Mark Allen 14e3d7b8b0 romio info: letting romio keep its internal setup
I'm restoring the info function pointers to the IO module
but allowing the function pointers to be NULL (eg in ompio).
And letting romio321 set its function pointers for those
routines.

This means the info system uses the new OMPI-level info
system for most things, but skips it and uses the pre-existing
romio info system just for the romio module.

It's possible to convert romio, but I went a ways down that
path and found it kind of convoluted.  Having pointers from
the lower level ADIO_File back to the higher level ompi_file_t
wasn't too bad, but I got stuck trying to figure out where/how
to register the infosubscribe_subscribe callbacks vs the way
initial k/v values are scattered around the romio code currently.

Signed-off-by: Mark Allen <markalle@us.ibm.com>
2019-09-03 14:08:19 -04:00
..
base io/base: fixes to file_delete selection logic 2018-08-27 16:01:48 -05:00
ompio romio info: letting romio keep its internal setup 2019-09-03 14:08:19 -04:00
romio321 romio info: letting romio keep its internal setup 2019-09-03 14:08:19 -04:00
io.h romio info: letting romio keep its internal setup 2019-09-03 14:08:19 -04:00
Makefile.am Revert "Update to sync with OMPI master and cleanup to build" 2016-11-22 15:03:20 -08:00