Peter Memishian wrote:
> > The notion of all such data being "historical" seems a bit odd. In
> > particular, especially on DEBUG systems, the administrator may not be
> > aware of when attach and detach operations are occurring. So the result
> > will be that kstats for occasionally-needed kernel modules will be
> > constantly getting cleared. That doesn't seem good to me.
>
> Huh. I'm not sure how the administrator doesn't know about
> attach/detach operations. Am I missing something? I thought DR was
> pretty much administrator driven.
The system is free to detach any dip that's not needed (e.g., by
periodically attempting to unload things). It may have become not needed
because of direct administrator action, or simply as a side effect of what
the running processes on the system are doing (e.g., what devices they
happen to have open).
Generally, all devices that are "interesting" are likely to have some
upper layer plumbed on them. Networking devices have IP. Disks have
filesystems, etc.
If the device isn't in use, then probably the historical data simply is
not interesting.
Also, the use of KSTAT_FLAG_PERSISTENT is itself, very inconsistent
among device drivers.
Just a thought.
-- Garrett
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
