| 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: Sat, 10 Jul 2010 16:14:54 -0600 From: Andreas Dilger <adilger@...ger.ca> To: Daniel Taylor <Daniel.Taylor@....com> Cc: ext4 development <linux-ext4@...r.kernel.org> Subject: Re: Repost (from LKML): EXT3 FS and 64K blocks error On 2010-07-09, at 16:32, Daniel Taylor wrote: > I guess we'll find out how well they work ;) we're putting them into > pre-production test now. The main reason is that we're building a NAS > that will see significant use as a media server (we hope) and we do see > a performance improvement with the larger file system blocks in our > engineering tests. I suspect that the reason you see better performance with ext3 and 64kB blocksize is due to the lower per-block allocation overhead. This issue is gone with ext4 due to extents and mballoc. >> Is there a particular reason why you care about this with >> ext3? Ext4 does provide a superset of the features in ext3... > > We're switching to ext4. I just thought someone might want to take > a look at the error message. I can do some more testing, next > week, if there are suggestions of what to try. It would be interesting to see if there are still differences in performance with ext4 + 64kB blocksize. At a minimum it is good for someone to test the 64kB blocksize support (which not many people can do), and it is worthwhile to know if there is still performance to be gained from large blocksize or not. Cheers, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists