Messages in this thread | | | Date | Sun, 26 Jun 2005 21:07:00 +0400 | From | "Artem B. Bityuckiy" <> | Subject | Re: reiser4 plugins |
| |
Christoph Hellwig wrote: > I'm a bit confused about what you're saying here. What does the 'vector' > in all these expressions mean? > > In OO terminology our *_operation structures are interfaces. Each particular > instance of such a struct that is filled with function pointers is a class. > Each instance of an inode/file/dentry/superblock/... that uses these operation > vectors is an object. > > What I propose (or rather demand ;-)) is that you don't duplicate this > infrastructure, and add another dispath layer below these objects but instead > re-use it for what it is done and only handle things specific to reiser4 > in your own code.
Just out of curiosity, could you please specify few exact examples with specific file/function names which duplicate the existing infrastructure. What do they duplicate and why? How should these functions be implemented on VFS? Ho should the the other FSes implement/ignore them? Why are you shure they will fit VFS well? etc.
Thanks.
-- Best regards, Artem B. Bityuckiy Oktet Labs (St. Petersburg), Software Engineer. +78124286709 (office) +79112449030 (mobile) E-mail: dedekind@oktetlabs.ru, web: http://www.oktetlabs.ru - 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/
| |