Michael J. Brim
Michael J. Brim
full set of related issues: #43 #45 #46 #47 #141 #176 #197 #216 #225 #248 #252 #262
[UnifyFS-Client-API-Proposal-v02.pdf](https://github.com/LLNL/UnifyFS/files/4042814/UnifyFS-Client-API-Proposal-v02.pdf) See attached pdf for current proposed API.
Here's the markdown writeup. https://github.com/LLNL/UnifyFS/blob/client-api-doc/docs/client-api.md
@tonyhutter I will be brief in my answer. Your concerns are noted, but you are focusing on the wrong use case. We have two main classes of users - parallel...
@clmendes What client configuration settings are you using for this test? Specifically, what are the UNIFYFS_LOGIO_SPILL_SIZE and UNIFYFS_LOGIO_SHMEM_SIZE values? I ask because the default values (1GB and 256MB) will not...
The `lio_listio()` wrapper now supports both read and write, with a mixture of regular and UnifyCR files. We still don't support asynchronous mode (i.e., `LIO_NOWAIT`) though.
@sandrain When a MPI program is launched standalone (i.e., not by an MPI launcher), the program will see rank=0 and a COMM_WORLD of size 1. Is your SLURM properly configured...
If you are using openmpi on your cluster, you need to have configured it to have slurm compatibility. See https://www.open-mpi.org/faq/?category=slurm#slurm-direct-srun-mpi-apps
MDHIM will initialize MPI if it has not been done yet. See meta/src/mdhim.c:98 . MPI_COMM_WORLD is a global variable that is initialized during MPI_Init()
Based on the code, we could pass NULL to `mdhimInit()` for the communicator. It will use MPI_COMM_WORLD (after init) if no communicator is provided.