Hi, Michael Shapiro wrote: >> Hi, >> >> I posted a new link ID management API document. It includes changes for >> comments received so far, plus a name change of the new service from >> network/linkmgmtd to network/dladmd, a name change from DLADM_OPT_TEMP >> to DLADM_OPT_ACTIVE, plus some language clean up. >> >> You can find it at: >> >> http://www.opensolaris.org/os/project/clearview/uv/link_id_management.pdf >> >> thanks for the comments, >> Dan > > Dan, > > Thanks for the posting the doc -- I'm still reading it, but one question > that I have at a high level is what the daemon itself is used for. In other > words, this document talks about configuring the links and naming them, > and storing that in SMF, and providing a nice API to examine things etc. > But if the configuration is stored in SMF, the API itself could just > be in effect a wrapper around libdlpi and libscf -- so what is the need > for the daemon? (I assume there's something else going on here, but I > didn't see it mentioned in the document -- sorry if I missed it) > > -Mike >
I added a sentence or two in the Introduction section about why we use the daemon approach. That was an oversight. The basic idea is we have both user land and kernel land components accessing SMF and allocating link ids. We felt a daemon was the best way to handle the problems of locking and coordination in this scenario. What I added was brief, more details are in the main UV design document. The change will appear in the next version of the document I post, which should be in the next day or two. thanks, Dan
