search

SerCeMan / jnr-fuse

FUSE implementation in Java using Java Native Runtime (JNR)
MIT License
367 stars 87 forks source link

Why not implement the inode interface provided by kernel fuse to replace the current path interface？ #158

Open T-TRz879 opened 2 years ago

T-TRz879 commented 2 years ago

I've seen the specification of kernel fuse before. For example, rename provides methods such as rename, renameat, and renameat2. I think that using inode of the parent directory for Rename is very effective and useful

T-TRz879 commented 2 years ago

@jenschurchill @melix @overheadhunter @czeidler

SerCeMan commented 2 years ago

Hey, @T-TRz879! Could you clarify the question? I'm not sure I understand it.

T-TRz879 commented 2 years ago

When I use go-fuse to implement my own file system. For example, in the rename method, the parameters of go-fuse contain parentPathNodeId. When I use our fuse rename, it's just srcPath and dstPath. If the directory is very deep, it's time-consuming. So can we implement the interface of the higher version of Lib fuse? I don't know if my understanding is correct？Thank's you reply to me :)

T-TRz879 commented 2 years ago

@SerCeMan

T-TRz879 commented 2 years ago

@SerCeMan