> - keep a separate VFSinode and FSinode slab cache
Yup.
> - allocate an enlarged VFSinode that contains the FSinode at the end,
> with the generic pointer in the VFSinode part pointing to FSinode
> part.
Please, don't. It would help with bloat only if you allocated these
beasts separately for each fs and then you end up with _many_ allocators
that can generate pointer to struct inode.
"One type - one allocator" is a good rule - violating it turns into major
PITA couple of years down the road 9 times out of 10.
-
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/