I greatly prefer function pointers to [possibly] generic obj management
code, to storing object sizes. Some filesystem is inevitably going to
want to do something even more clever with inode allocation. My method
gives developers the freedom to experiement with inode alloc to their
heart's desires, without affecting any other filesystem.
> Also, having the inode point at itself is a little, hmm, 'what's wrong with
> this picture', don't you think?
gone in the updated patch :)
-- Jeff Garzik | Alternate titles for LOTR: Building 1024 | Fast Times at Uruk-Hai MandrakeSoft | The Took, the Elf, His Daughter and Her Lover | Samwise Gamgee: International Hobbit of Mystery - 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/