On 07/01/09 08:46, Peter Memishian wrote:
> They are certainly not just for debugging. Many drivers will have
> private properties that relate to features of their h/w. These will be
> documented for sysadmin use but being able to enumerate them would, I'm
> sure, be a highly useful feature. In fact, it would be really useful if
> a description could be associated with each property so an admin could
> not only enumerate the properties, but get some idea of what they do.
This is exactly the sort of shantytown we were hoping to avoid building.
Having seas of unique private properties in each driver is simply not a
sustainable model for administering Solaris. If there are private
properties that the average administrator needs to set (e.g.,
configuration knobs, and not workarounds for disabling brokenness), I'd
hope many of those things are generic enough to apply to more than just
one driver and therefore should be added to the framework proper. If they
are not that generic, I'd encourage driver writers to explore other
options like auto-configuration. I know this isn't always possible, but
the answer is *not* to build a wet bar in the private property lifeboat.
Like it or not, the fact is that there *are* devices that need unique
tunables, either for performance or (in some cases) even functionality
reasons.
-- Garrett
_______________________________________________
networking-discuss mailing list
[email protected]
