Does that mean that all Fuse filesystems automatically gets this huge boost ?
In the beginning, only privileged ones will be allowed to run in pass-through mode. But goal/roadmap calls for all FUSE filesystems eventually to have this near-native performance.
I feel I should know this in my bones after so many years, but does 'privileged' in kernel context also include 'sudo/sudo su' elevated users ? I wonder if the kernel distinguish between pure root, and elevated user ..or if it even matters here ?
Anyway, this is cool. There's a ton of crazy file systems that just didn't pan out bc of speed issues. I'll just leave these links to filesystems.
https://github.com/libfuse/libfuse/wiki/Filesystems A ton of cool ideas!.. I need my AI to have access via fuse. https://en.wikipedia.org/wiki/Filesystem_in_Userspace?lang=en less crazy systems but probably stable projects
Thanks for sharing the info!
sudo allows so run actions as root, so I would say yes.
But a privileged filesystem might not be invoked by the user, it may be a process running as root.
How would the update affect stuff like a GoCryptFS volume which I mount and use periodically but not all the time? Would those files be processed much faster than previously?
This is the best summary I could come up with:
The FUSE passthrough mode that's been years in the making for better performance was merged upstream today for the in-development Linux 6.9 kernel!
Last month I wrote that FUSE passthrough might land for Linux 6.9 after noticing the patches finally appear in FUSE.git's "for-next" branch.
This feature was indeed sent in as part of the FUSE updates for Linux 6.9 and today Linus Torvalds merged it upstream.
The FUSE merge for Linux 6.9 sums up the feature as: Add passthrough mode for regular file I/O.
This allows performing read and write (also via memory maps) on a backing file without incurring the overhead of roundtrips to userspace.
For now this is only allowed to privileged servers, but this limitation will go away in the future FUSE for Linux 6.9 also fixes up an interaction issue in direct I/O mode with memory maps, exposes file-system tags through sysfs for VirtIOFS, and various other fixes.
The original article contains 248 words, the summary contains 153 words. Saved 38%. I'm a bot and I'm open source!
Note: Android kernel has had this since 12 because FUSE is used to enforce permissions and to emulate legacy storage types.
https://source.android.com/docs/core/storage/fuse-passthrough
From the patch back in 2016:
There is also a significant cpu/power savings that is achieved which is really important on embedded systems that use fuse for I/O.
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0