On Fri, Jun 20, 2025 at 7:50 PM Viacheslav Dubeyko <Slava.Dubeyko@xxxxxxx> wrote: > > Nowadays, VFS and memory subsystems are C implemented functionality. And I don't > think that it will be changed any time soon. So, even file system driver will be > completely re-written in Rust, then it should be ready to be called from C code. That is fine and expected. > Moreover, file system driver needs to interact with block layer that is written > in C too. So, glue code is inevitable right now. How bad and inefficient could > be using the glue code? Could you please share some example? Please take a look the proposed VFS abstractions, the filesystems that were prototyped on top of them, and generally other Rust code we have. As for "how bad", the key is that every time you go through a C signature, you need to constrain yourself to what C can encode (which is not much), use unsafe code and other interop issues. Thus you want to avoid having to go back and forth all the time. Thus, the idea is to write the filesystem in Rust using abstractions that shield you from that. Cc'ing other potentially interested/related people. Cheers, Miguel
