Correct me if I am wrong:
What exists currently in VFS are vector instances, not classes. Plugins,
selected by pluginids, are vector classes, with each pluginid selecting
a vector class. You propose to have the vector class layer (aka plugin
layer) in reiser4 export the vector instance to VFS for VFS to handle
for each object, rather than having VFS select reiser4 and reiser4
selecting a vector class (aka plugin) which selects a method.
If we agree on the above, then I will comment further.
Christoph Hellwig wrote:
>On Wed, Jun 22, 2005 at 06:24:32PM +0400, Alexander Zarochentsev wrote:
>
>
>>Reiser plugins are for the same. Would you agree with reiser4 plugin design
>>if the plugins will not dispatch VFS object methods calls by themselves but
>>set ->foo_ops fileds instead? I guess you don't like to have the two
>>dispatching systems at the same level.
>>
>>
>
>That is exactly the point I want to make. I haven't looked at the design
>in detail for a long time, but schemes to allow different object to have
>different operation vectors is a good idea. We already have that to
>varying degrees in all filesystems, and making that more formal is a good
>thing.
>
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
