On Tue, Jun 20, 2006 at 10:43:16AM +0100, Steven Whitehouse wrote:
> As a further suggestion, I wonder do we really need i_private at all?
> Since we have sb->s_op->alloc_inode and inode->i_sb->s_op->destroy_inode
> if all filesystems did something along the following lines:
> 
> struct myfs_inode {
> 	struct inode i_inode;
> 	...
> };
> 
> #define MYFS_I(inode) container_of((inode), struct myfs_inode, i_inode)

That would work for filesystems but we would also need some solution
for device inodes.  (And at that point, yes, we could move it into
device-specific union, but as I've already noted, that doesn't buy us
anything currently.)

It's worth thinking about, but for that amount of effort it might be
have better ROI to work on moving the address space out of the inode
given that many/most inodes in memory are caching stat information,
not pages.

						- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/