-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
NFS engine via libnfs #1216
NFS engine via libnfs #1216
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly style but I think there might be some local changes that need to be removed...
Pulled, thanks. |
Version 3.30:
But ./configure --disable-nfs work without errors. |
@tarasglek Does look like the configure additions are fairly random and broken, care to fix it up? |
Happy to fix it, but wont have time for 2 weeks. |
ping |
@tarasglek please get this sorted out, it's been months now. If not, I'm going to revert the series. |
@VVD does it work in current -git now? |
@axboe, in 3.31 P.S. Last several months github doesn't send me emails if I subscribed on issues… |
For scale-out storage, driving load through the kernel requires a lot more resources than driving load from user-space, thus libnfs binding came into being.
For now this is just block IO. Eventually I'd like to let fio drive metadata operations too.
We love fio at Pure Storage. Between various kernel modes, S3 and libnfs fio gives us a nice way to validate storage performance.