Quoth Garrett D'Amore on Fri, Jun 01, 2007 at 09:55:37AM -0700: > So what I've been trying to drive Brussels toward is providing a > *single* API in drivers (setprop/getprop) for doing all this, and let > Brussels do details like supporting kstat, legacy NDD ioctls, and the > newer dladm support ... all on top of the setprop/getprop API. > > (Note at this point I'm talking about the driver/kernel bits of > Brussels.... the userland access to certain properties via dladm is just > a bonus, IMO. :-) > > If this happens, then it will bring a great deal of uniformity to the > administration of GLDv3 drivers, that is currently lacking.
Data access uniformity is appealing, but sometimes the framework needs to be aware of differing semantics. SMF unified the data access interfaces for configuration and status, but without a way to distinguish between them, the framework (and in some cases, consumers) had to hardcode which names had certain semantics. This is one of the problems I'm fixing with the enhanced profiles project. David _______________________________________________ networking-discuss mailing list [email protected]
