Native IME Data Layer
S-01504
As a Tullow Geophysicist I want my code to directly utilise the IME (if available) because I want my code to run as efficiently as possible.
PreDev Notes:
While IME supports transparent access through both POSIX and MPI-IO (using a modified version of ROMIO), it gets the best possible performance using the IME Native API. This is illustrated by the IME functional chains below:
-
POSIX (using IME FUSE client):
- Application --> Kernel --> IME FUSE --> IME Client --> IME Server
-
MPI-IO:
- Application --> MPI-IO --> IME Client --> IME Server
-
Native IME API:
- Application --> IME Client --> IME Server Information about the IME Native API, including calls and sample code, are in GoogleDrive in PDF "IME v1.0 Developer Guide DRAFT" (Reference Papers/IO/Hardware/DDN/). To implement native IME support, will require creating another abstraction of the data layer. Maybe not as part of this story, but there should eventually be some tests comparing performance of Native IME API vs MPI-IO with IME
Implementation Notes:
ADDME
System Test Changes:
ADDME
Bug Fixes:
ADDME
C++ API Changes:
ADDME
C API Changes:
ADDME
Success Criteria:
ADDME
CREATED ON 06/09/2016
Edited by Christopher Werner