-
Notifications
You must be signed in to change notification settings - Fork 29
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
FUSE? #211
Comments
I understand that I was not very precise in terminology. Because fuse is about userspace. But I think it is clear that I want to create my own file system |
hi @Jipok, it's actually on my long-term TODO list ;-).. we would need to create bindings for that.. if you are interested in implementing this, I could definitely help.. a good starting-point, IMHO, would be to study the in-kernel FUSE support and figure it out what kernel APIs we would need to provide to the scripts..
we would need to measure.. and it would be a good academic experiment, IMHO.. my gutting feeling is that we indeed might be more efficient for some use cases |
Oh no. I never want to go back to C (or C++) again. If I do anything for the kernel, it will be on zig. That was a theoretical question. I'm actually more interested in whether an overlayfs-like fuse might benefit from moving into the kernel. Your project could easily allow me to quickly try out the concept instead of suffering through kernel module development. Maybe I'll wait until you implement fuse and access to the file system. |
well.. it should be mostly boiler plate code and it will set you free from C ;-)
it might take a while then.. heh =) |
Will it be possible to implement fuse in the kernel in the future?
And does it make sense at all, i.e. will it be more efficient than userspace implementation?
The text was updated successfully, but these errors were encountered: