On (03/19/08 14:10), Garrett D'Amore wrote: > > Are those "well-known" properties? (I.e. do more drivers than just bge > make use of those names?) If so, then you should just remap it in the
it's not uniformly supported across drivers. And the lack of uniformity was the reason PSARC 2007/429 came up with flowctrl. But there are other outliers.. nge, for example has a bunch of parameters for bcopy/dma thresholds. Yes, these should be auto-tuned, but they are not, and until they are auto-tuned, we need some way to control them. > So, in retrospect (I think I suggested this earlier), I'd actually > welcome a change that did: > > 1) offered only well-known names via NDD > 2) make all other private properties only available via dladm If we are going to do this, then we may as well skip all of the ndd compat effort, as Joost suggested. > 3) as a consequence of #1 above, you could actually skip the separate > registration of property names for now, until another consumer of them > (dladm?) exists > > Something to think about, at least. > I think there is some value in having mac_register_private_prop interfaces. --Sowmini
