RFC: expensive lookup for unlink
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Hello,for a network filesystem one should try to avoid all remote operations, if possible. So when I just want to unlink a file, it does not make too much sense to first send a lookup and once the dentry is fully established to unlink the file.
I think the simplest way to solve that is just to add a another nameidata flag (LOOKUP_UNLINK) and the file system may then just ignore the lookup request and fill in fake values.
Or are there any other suggestions to avoid a rather useless network-lookup + network+unlink, so so combine it into one step? Thanks, Bernd -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Ext4 Filesystem] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [CEPH Filesystem]