> The policy seems to distribute dir inodes uniformly on all block
> groups. Why do we want to do this? Isn't it better to create a dir
> inode close to its parent dir inode?
Directories can, and frequently are, moved. If you kept the dir inode close to its parent dir inode, you'd have to move dir inodes around every time you move directories. Less is more.
Keeping the dir inodes uniform means the time to perform a name->inode lookup is relatively the same regardless of directory. While admittedly this does not always yield the fastest performance, in this case we prefer consistency over speed.
I'm sure there are other good reasons too, but these two are enough to justify it.
Joseph D. Wagner
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
