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
| ||
|
Date: Wed, 21 Apr 2010 01:44:34 +0100 From: Jamie Lokier <jamie@...reable.org> To: Phillip Susi <psusi@....rr.com> Cc: linux-fsdevel@...r.kernel.org, Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: readahead on directories Phillip Susi wrote: > I have been trying to improve boot times with ureadahead and have > identified a period of time of almost zero IO throughput caused by calls > to open() blocking during name lookup while fetching directory blocks. > At first I thought this could simply be fixed by calling readahead() on > the directories first before open()ing all of the normal files for > readahead. > > Unfortunately it seems that readahead() fails when called on a > directory. I was wondering if I could get some help understanding why > this is, and how it could be fixed. readahead() doesn't make much sense on a directory - the offset and size aren't meaningful. But does plain opendir/readdir/closedir solve the problem? -- Jamie -- 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