Ryan Hope wrote: > So the purpose of that "plugins" document is just to "defend" the > present state of the reiser4 code? > Yes. In particular. Plugins stuff is a way of data storage optimization and its removing definitely would be a mistake. What can arise here again is complaints about "layering violation". However, addressing them doesn't necessarily mean removing the whole plugin stuff. I hope that this document will help such discussions to be more constructive. Thanks, Edward. > On Sat, Aug 2, 2008 at 6:56 PM, Edward Shishkin > <edward.shishkin@xxxxxxxxx> wrote: > >> Ryan Hope wrote: >> >>> Can you explain a little more what this "plugin design documentation" >>> actually is and how it supposed to help? >>> -Ryan >>> >>> >>> >> This document is to define plugins, etc primitives (like conversion >> of run-time objects) used in reiser4, and to describe all reiser4 >> interfaces, so that it will be clear that VFS functionality is not >> duplicated, there are not VFS layers inside reiser4, etc. (many items >> are devoted to interaction between VFS and reiser4). >> I am sorry, but these concepts (which are very central) have not been >> worked out carefully enough at the moment of this 3-year-old review: >> http://kerneltrap.org/node/5330 >> >> Edward. >> >> >>> On Fri, Aug 1, 2008 at 6:40 PM, Edward Shishkin >>> <edward.shishkin@xxxxxxxxx> wrote: >>> >>> >>>> Ric Wheeler wrote: >>>> >>>> >>>>> Theodore Tso wrote: >>>>> >>>>> >>>>>> On Fri, Aug 01, 2008 at 12:34:53PM -0400, Ryan Hope wrote: >>>>>> >>>>>> >>>>>> >>>> Hi, I am here :) >>>> Join our mailing list: >>>> >>>> http://vger.kernel.org/vger-lists.html#reiserfs-devel >>>> http://marc.info/?l=reiserfs-devel&r=1&w=2 >>>> >>>> There are many interesting tasks to resolve/investigate.. >>>> >>>> >>>> >>>>>>> Hmmm, removing the plugin support might not be so hard.... I might >>>>>>> have to try this... >>>>>>> >>>>>>> >>>> Please, don't try to do this. >>>> >>>> I am working on the plugin design document. It will be ready >>>> approximately in September. I believe that it'll address all the >>>> mentioned complaints. >>>> >>>> >>>> >>>>>>> I am not impressed with btrfs yet. >>>>>>> >>>>>>> >>>>>>> >>>>>> Well, if you're going to work on reiser4 (and I think there were other >>>>>> people who had also expressed interest/plans to work on it; you might >>>>>> try doing a search on the various mailing lists so you can coordinate >>>>>> with them and avoid duplicating work), my suggestion to you would be >>>>>> to find the comments that were made by the reviewers way back when, >>>>>> and make sure those comments have been addressed. >>>>>> >>>>>> Then, re-requests a code review, and promise that you won't abuse, and >>>>>> insult the integrity and impugn the motivations of the reviewers >>>>>> >>>>>> >>>> Well, Ted, I'll promise ;) >>>> We'll adhere strictly the propositional logic in the review thread.. >>>> >>>> Thanks, >>>> Edward. >>>> >>>> >>>> >>>>>> like >>>>>> Hans did, and hopefully after they review the code, fix those problems >>>>>> as well. Then you can try resubmitting for inclusion. >>>>>> >>>>>> Best regards, >>>>>> >>>>>> - Ted >>>>>> >>>>>> >>>>>> >>>>> My most up to date information is that Edward is still actively >>>>> working on reiser4.... >>>>> >>>>> ric >>>>> >>>>> >>>>> >>>>> >>>> >>> >> > > -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
