-
Notifications
You must be signed in to change notification settings - Fork 26
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
Leverage O_DIRECT #5
Comments
Seems doable, I'll have a look into it. |
O_DIRECT doesn't work with ZFS yet. So this would still have to fall back when unavailable. |
Rather than using |
Implemented shodanshok's POSIX_FADV_DONTNEED, which reduces cache pollution substantially. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would it be possible to add an option to to open devices for reading and writing with O_DIRECT? This would prevent the large reads and writes to devices that bdsync does from polluting the buffer cache.
You can use old method of mapping a raw device to work round this but it's been deprecated since Linux 2.6.3
The text was updated successfully, but these errors were encountered: