James Carlson wrote:
Garrett D'Amore writes:
I've also found a number of drivers that don't strictly conform to the
ieee802.3(5) documented values.
File bugs; they're supposed to support them.
Extracting some consistency out of the
current anarchy is one of the goals that I see for Brussels.
Brussels, I think, aims at configuration parameters (the last bastion
of ndd and driver.conf) rather than status inquiries like this.
One can take the (quite reasonable, IMO) view that kstats, ndd tunables,
and even driver.conf properties all are just "properties" of one form or
another, some writeable, and some not.
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.
-- Garrett
_______________________________________________
networking-discuss mailing list
[email protected]
