| 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: <E1JDKcK-0003cu-Ps@be1.7eggert.dyndns.org> Date: Fri, 11 Jan 2008 15:12:16 +0100 From: Bodo Eggert <7eggert@....de> To: Abhishek Rai <abhishekrai@...gle.com>, ak@....de, ebiederm@...ssion.com, rdreier@...co.com, gregkh@...e.de, airlied@...net.ie, davej@...hat.com, mingo@...e.hu, tglx@...utronix.de, akpm@...ux-foundation.org, arjan@...radead.org, ?missing closing '"' in token?"Barnes", Jesse <jesse.barnes@...el.com>, davem@...emloft.net, linux-kernel@...r.kernel.org, ?missing closing '"' in token?"Siddha", Suresh B <suresh.b.siddha@...el.com>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [PATCH] Clustering indirect blocks in Ext3 Abhishek Rai <abhishekrai@...gle.com> wrote: > Putting metacluster at the end of the block group gives slightly > inferior sequential read throughput compared to putting it in the > beginning or the middle, but the difference is very tiny and exists > only for large files that span multiple block groups. Just an idea: What about putting it into the end of the previous block group (except for the first group, off cause) and starting to read the block group a little earlier (readahead/~before)? I imagine it might be about as good as placing it at the beginning while avoiding the fragmentation. -- 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