On 2012-06-20, at 10:50 PM, Norbert Preining wrote: > On Mi, 20 Jun 2012, Eric Sandeen wrote: >> Hm. Upstream coreutils fixed this for rm and some other ops: > > Ok, I see. > >> sorted took 2.6s, unsorted took 52s. > > Got the idea, and tried it now myself not with ls etc, but > with the program that generates the caos, and yes, stracing it > gives the same result, getdents and the followed stats are all > *not* in inode order. > > So that means, it should be fixed in glibc? Right? Ouuchhh... > > That means that this behaviour is for *each* program using getdent > etc ... > > Do you have any suggestions? Is there a way to force readdir (I guess > most people use readdir instead of getdents directly) to iterate > in inode order? That's what the LD_PRELOAD library that Eric referenced does - you can load it for any application, and it will sort the dirents in inode order. It would definitely be better to do this in glibc, though we've also been discussing on occasion doing this inside ext4 for small directories. Cheers, Andreas -- 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
