James Dinan
James Dinan
## Summary Messages below the FI inject and Portals volatile thresholds are buffered by the networking layer and achieve (especially relevant for blocking puts and non-fetching AMOs) immediate local completion....
Organize the source code into subdirectories, like: * src/ * bindings/ * internal/ * transport/
Perform a collective check for symmetry (base, size) of the data segment. This should generate a warning message (symmetric data segment is borked, but heap should still work) in scenarios...
Others have reported XPMEM leaking pages. Does it leak pages with SOS, too? ``` $ cat /proc/xpmem/global_pages all pages pinned by XPMEM: 6410705 all pages unpinned by XPMEM: 6410700 ```
Completion counters are a finite resource on some platforms. Make separate put/get completion counters a per-context option (e.g. enabled on default context and disabled by default on others).
The manpages have a extra empty lines when viewed with vimpager (https://github.com/rkitover/vimpager). Could be an issue with vimpager, but I've been using it for years and haven't run into this...
Direct load/store accesses to pSync in collectives (e.g. assertions that overlap with remote atomics) may violate Portals/libfabric memory model.
Several collectives, including the dissemination barrier implementation of the new sync operation (#489) call ```shmem_internal_quiet```. Especially in the case of sync, this is undesirable. The quiet in sync can't be...
Lock API calls quiet more than is required by the spec (e.g. before releasing the lock). Investigate and fix.
Extend new infrastructure to check min/max, etc. for parameters passed through env vars.