-
Notifications
You must be signed in to change notification settings - Fork 902
new fbtl using direct I/O #1290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Test FAILed. |
f974c16
to
c96ea38
Compare
Test FAILed. |
A previous commit updated the one-sided code to register the state region only once. This created an issue when using the scratch lock with fetching atomics. In this case on any rank that isn't local rank 0 the module->state_handle is NULL. This commit fixes the issue by removing the scratch lock and using a fragment pointer instead. Fixes open-mpi#1290 Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>
34e4351
to
043e37a
Compare
fix a typo
@edgargabriel Looks like Travis actually found an error here in the OS X build. You can see the build error at the bottom of the full / raw build log: https://s3.amazonaws.com/archive.travis-ci.org/jobs/101080685/log.txt |
hm, the error that I see does not come from directio fbtl, but from On 1/8/2016 10:05 AM, Jeff Squyres wrote:
Edgar Gabriel Tel: +1 (713) 743-3857 Fax: +1 (713) 743-3335 |
Not merging the branch, the performance of the direct I/O component is disappointing. Keeping the code in the branch however around. |
v2.x: mpisync: Fix a compilation error.
No description provided.