Join GitHub today
Any plans to support nfs v4? #156
When monitored my code for the nfs rpc calls with nfsstat, this is my find - There is one lookup call per one NFS_opendir call. I guess lookus are slower with NFS v3. NFS v4 documentation clearly mentions better caching mechanisms.
This is not a problem if the avg no of files per directory is more than a threshold. But if avg no of files per directory is lesser (I've tested for two fiiles per directory), libnfs code performs badly as compared to scandir.
So just wanted to check how complex it would be to support v4 through libnfs
NFSv4 will not make any difference here.
What you might be seeing is that a normal nfsv3 client and libnfs does
Libnfs does does do directory caching and will return data from cache
This is the Lookup call you see where it fetches the mtime for the
(boring detail, but Nfs readdirplus can only return at most 8kb of
Legacy in nfs clients does do the caching differently though.
That means that if an nfsv3 client has stored a directory in cache, then if
This is what the nfsv4 rfc means with the wording "Just as in the cases of
It is possible to change libnfs to behave more like traditional nfs clients
On Mon, Nov 14, 2016 at 10:42 PM, dhanumuli firstname.lastname@example.org