On Sat, Dec 08, 2001 at 11:28:00PM +0300, Hans Reiser wrote:
> Using a union of filesystems, that might not even be compiled into the
> kernel or as modules, in struct inode is just..... bad.
> It is really annoying when the filesystems with larger inodes bloat up
> the size for those who are careful with their bytes, can we do something
> about that generally?
I believe it has been desided to solve this either by:
* including a filesystem-specific pointer in the general inode
* have the filesystem build the inode, and include all the general inode
variables in it's data-structure.
If it's not alreaddy done in 2.5 I think it's just a question of time.
-- Ragnar Kj°rstad Big Storage - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:13 EST