On (10/04/07 17:03), James Carlson wrote: > > Let me suggest an alternative. Since Nevada hasn't released and > likely isn't going to release for some time, and since that's where > you're headed, I would recommend providing the bulk of these as > "Committed" interfaces, and making only a tiny minority of > questionable ones "Uncommitted." > > You can still change them in incompatible ways any time you like so > long as the bits haven't been baked into a release. The stability > levels refer to releases (major/minor/micro), and not to mere builds > or evaluation copies.
Ok. I think the only ones where we expect possibly volatile behavior is flowctrl; I'll mark the rest as Committed > > > > - Will use of ndd for drivers eventually go away? Is that part of > > > the plan or will we carry compatibility forever? > > > > yes! Absolutely! this will be covered by the ndd compatibility > > component of Brussels. See Section 5.2 of > > http://cr.opensolaris.org/~sowmini/commitment.materials/brussels.pdf > > Which is it? Going away or staying forever? going away. The idea is still to catch and deflect these ioctls at the dld/mac layer, only contact the driver for setting/getting properties. The legacy support will only be implemented for drivers that currently have ndd interfaces i.e., new drivers should not, and must not, be implementing ndd support. Section 5.2 of the design doc provides a sketch of this process. The details of the interfaces will be provided with the ndd compat case itself. > I think the ndd administrative interfaces on drivers are a wart, and > it'd be nice at some point to nudge users away from them (when there's > a better alternative, such as dladm) at first, and then to _force_ > them away by breaking ndd. > > I don't see an obsolescence plan here. Did you want to see this in the 20q.txt (some of it is there in answer to the question "what are the clients over which a change should be managed", but I could provide more details if you feel it is needed (without confusing the deliverables associated with 2007/429 itself).
