That should be quite easy to quantify then. Move the readdir and stat=20
call next to each other in the sources, pass the struct stat around if=20
necessary, and then count the stat calls which do not originate from th=
e=20
stat following the readdir call. Of course we'll also need the actual=20
improvement which can be achieved by combining the calls. Given the=20
inodes are cached, is there more overhead then finding the right inode?=
=20
Note that is rsync doesn't already use fstatat() it should do so and=20
this means then that there is no long file path to follow, all file=20
names are local to the directory opened with opendir().
My but feeling is that the improvements are minimal for normal (not=20
cluster etc) filesystems and hence the improvements for kernel.org woul=
d=20
be minimal.
--=20
=E2=9E=A7 Ulrich Drepper =E2=9E=A7 Red Hat, Inc. =E2=9E=A7 444 Castro S=
t =E2=9E=A7 Mountain View, CA =E2=9D=96
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel=
" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
