lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 25 Jul 2014 16:30:32 -0400
From:	Trond Myklebust <>
To:	Steven Whitehouse <>
Cc:	Zach Brown <>, Abhijith Das <>,
	linux-fsdevel <>,
	cluster-devel <>,
	Linux Kernel mailing list <>
Subject: Re: [Cluster-devel] [RFC] readdirplus implementations: xgetdents vs
 dirreadahead syscalls

On Fri, Jul 25, 2014 at 4:02 PM, Steven Whitehouse <> wrote:
> Hi,
> On 25/07/14 19:28, Zach Brown wrote:
>> How do the file systems that implement directory read-ahead today deal
>> with this?
> I don't know of one that does - or at least readahead of the directory info
> itself is one thing (which is relatively easy, and done by many file
> systems) its reading ahead the inodes within the directory which is more
> complex, and what we are talking about here.

NFS looks at whether or not there are lookup revalidations and/or
getattr calls in between the calls to readdir(). If there are, then we
assume an 'ls -l' workload, and continue to issue readdirplus calls to
the server.

Note that we also actively zap the readdir cache if we see getattr
calls over the wire, since the single call to readdirplus is usually
very much more efficient.

Trond Myklebust

Linux NFS client maintainer, PrimaryData
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists