On Thu, 28 Jun 2001, Andrew Morton wrote:
> So the rule should be: if your private inode info is larger
> than ext2's, you should allocate it separately.
Wrong. There is /proc. There is devfs or its equivalents. There are
pipes and sockets.
"bloated inodes are OK since ext2 is all that matters" is bogus. Many
things are overcomplicated precisely because struct inode is too large.
BTW, cost of extra dereferncing is trivial - when we access ext2-specific
part of inode we usually
a) do it more than once in a given function
b) access a lot of stuff outside of struct inode.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]