Older system/kernel compatibility #45
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
On these older systems, is there a good justification to use sendfile vs. the read/write engine (i.e., by setting posix-io=rw)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use sendfile instead of copy_file_range when compiling on systems with kernels too old to support copy_file_range and glibc too old to emulate it.
When using auto-install.py, enable passing cmake arguments to dependencies. Also only attempts to import some non-stock python libraries when necessary.
(I must pass
-DCMAKE_NO_SYSTEM_FROM_IMPORTED=ONfor compiling w/ custom mpi installs on some systems)