> I just read this. The part that concerns me is in 2.3: > > "... Unlike legacy utilities such as ndd, the semantics and allowed > values of each property will be known to dladm, reducing the > incidence of administrative mistakes:" > > Does this mean that I don't have any way to use a custom property in > my driver? (eg, dladm set-prop -p fluxcapacitor=on myri10ge0). Or > does it mean that the driver needs to supply the semantics?
Our focus has been on providing a uniform way to administer common properties, rather than to provide a mechanism to introduce one-off properties. In many respects, one-off properties are the enemy of an approachable system, especially since they (a) put a burden on the administrator both to recall and adjust them (on a per-driver basis), and (b) increase the number of configurations that must be tested. Are you absolutely sure you need a custom property? Or is there a possibility of self-tuning? -- meem _______________________________________________ networking-discuss mailing list [email protected]
