On Mon, Jun 22, 2009 at 10:46:17AM +0900, Toshiyuki Okajima wrote: > I have been reviewing the logic around dir_index(fs/ext4/dir.c > fs/ext4/namei.c) for the sake of performance and quality > improvement. Then I found this bug. Sorry, therefore it is not a > result of the real test. I've started doing some testing on the e2fsprogs side, and fixed some problems in for the upcoming e2fsprogs 1.41.7, but both the kernel and e2fsprogs currently don't officially support a blocksize larger than 64k. At least e2fsprogs in the git tree will mke2fs that passes e2fsck for a 128k block filesystem; this is *not* yet true for 256k block filesystems (but it requires some commits in the 64k block numbers patches which I don't want to merge into the maint branch). Are you aware of any patches that enable an IA64 system to support a page size greater than 64kB? (And whether any customer would actually want to use them, given the downsides of very large page size?) The issue is that Linux doesn't support filesystem block sizes > than the page size. In any case, I don't mind adding patches that attempt to make it better to support large block sizes; I don't really want to claim that we support it until we can actually fully test for that feature, though. Is it your intent to actually try to provide support for this at some point? I'll help you if you are, but you'll have to do the testing, since I don't have access to an IA64 platform that might be able to support these sorts of large pages. Thanks, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
