Sebastien Roy wrote:
Darren Reed wrote:
I'd encourage the document to talk about how to do this.
For example, talk about what type of module is best here (character
device, STREAMS, etc), what they should do in entry points, exit
points, what interfaces they need to implement and so on.
Have you read the MAC-Type Plugin design document? That document
contains these details. The architectural documents that describe the
external interfaces are forthcoming shortly.
No, I was reading the IP tunnel bits.
The "MAC Type Independent Nemo Architecture" document doesn't mention
whether it is consolidation private, project private or...
I think what I'm looking for is here, in section 7 (Interface Table):
http://www.opensolaris.org/os/project/clearview/nemo-mactype-plugins.txt
and "Consolidation Private" is a good place to start, so long as it is
available for contracts.
...
Hmm, maybe your definition of design isn't the same as mine, which is
fine. To me (actually, to most of the Solaris community), design
documents describe the internal design of an implementation, including
how implementation specific pieces work. This allows others to
understand the implementation and why particular implementation
decisions were taken.
Quite possibly this is why I've asked the questions I have and made the
comments I have.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
