rusty@rustcorp.com.au (Rusty Russell) wrote on 12.07.02 in <20020711235822.8B2494849@lists.samba.org>:
> I noted previously that you can do it if you do restrict the interface
> to "one module, one fs" approach, as you've suggested here. Al
> corrected me saying that's not neccessary. It's possible that he's
> come up with a new twist on the "freeze-the-kernel" approach or
> something.
>
> Al has scribbled in the margin that there's a clever solution, let's
> hope he doesn't die before revealing it. 8)
I suspect it's simply generalizing the concept of a registered interface.
Suppose you had *one* data structure that described *all* interfaces this
module supports, and you call *one* (un)register function to do the job.
Then, you are essentially in the same situation as you are today when you
support exactly one fs, no?
Of course, this registration abstraction must be powerful enough to do
everything you can do today without it, but that's just a SMOP ...
MfG Kai
-
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/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:22 EST