mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 16:31:02 +03:00
ec5a6ef1f0
Summary: The NFS readdir turns out to be pretty similar to the FUSE one, with a couple of differences. For one, it only populates the directory entry name, it also puts a limit on the total size of the serialized result, including all the NFS/XDR overhead. It is not specified if the . and .. entries need to be returned, but since the NFS spec is usually pretty explicit about these and makes it clear that this is for the most part a client burden, I didn't add these. I may have to revisit this later when I get to manually browse a repository. Since the READDIR RPC doesn't populate any filehandle, the client will have to issue a LOOKUP RPC for each entries, potentially leading to some inefficiencies. A future diff will implement the READDIRPLUS to fix these. Reviewed By: chadaustin Differential Revision: D26802310 fbshipit-source-id: b821b57021d0c2dca33427975b1acd665173bc5c |
||
---|---|---|
.. | ||
benchharness | ||
benchmarks | ||
cli | ||
cli_rs | ||
config | ||
docs | ||
fuse | ||
inodes | ||
journal | ||
model | ||
monitor | ||
nfs | ||
notifications | ||
prjfs | ||
py | ||
rocksdb | ||
scripts | ||
service | ||
sqlite | ||
store | ||
takeover | ||
telemetry | ||
testharness | ||
third-party | ||
utils | ||
CMakeLists.txt |