[Gnu-arch-users] Re: readdir() optimization for ext3/Linux 2.6

[Miles Bader]

Florian Weimer <address@hidden> writes:
> I've just finished a patch for Maildir support in mutt CVS that sorts
> the directory entries by inode before opening them.  Without this
> optimization, you incur a tremendous seek overhead because due to the
> new directory hashing, readdir() returns the entries in random order.

Isn't this filesystem-specific?  How on earth do you tell what sorting
order is best for a given directory?!?

-Miles
-- 
I'd rather be consing.