| lists.openwall.net | 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100422070129.GB10662@cynthia.pants.nu> Date: Thu, 22 Apr 2010 00:01:29 -0700 From: Brad Boyer <flar@...andria.com> To: Jamie Lokier <jamie@...reable.org> Cc: Phillip Susi <psusi@....rr.com>, linux-fsdevel@...r.kernel.org, Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: readahead on directories On Wed, Apr 21, 2010 at 11:06:12PM +0100, Jamie Lokier wrote: > For specific filesystems, you could do it. readahead() on directories > is not an unreasonable thing to add on. > > Generically is not likely. It's not about blocking, it's about the > fact that directories don't always consist of data blocks on the store > organised similarly to a file. For example NFS, CIFS, or (I'm not > sure), maybe even reiserfs/btrfs? Some non-UNIX file systems don't have anything that looks like a directory either. Just as an example, HFS and HFS+ both have a single catalog file for the whole file system. The directory listing method involves walking the tree from this file and picking a few fields out of each record matching the appropriate parent directory. This would make it hard to do something generic, although it would be possible to readahead some range of blocks of the catalog and produce a similar effect. This would really need to be FS specific, and the current readahead impementation is mostly common code. Brad Boyer flar@...andria.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists