On Tue, Jul 21, 2009 at 2:48 PM, Darren Reed<[email protected]> wrote: > Peter Tribble wrote: >> >> What does this look like in the global zone? Can I see all of the >> separate stack instances? > > No.
Bother... >> How are they identified? Just as separate kstat instances? In that >> case, how do I map each >> instance to a given stack instance and thus to a zone? >> > > What is the nature of this question? > Administrative or programming? > If it is administrative, I think the answer to th above two questions will > answer the rest > of your questions here. If I can't see the kstats in the global zone (why not?) then it doesn't matter. But as someone who writes programs to display kstats, it would be nice to be able to connect a given kstat with its object. >>> These kstats will be delivered under module "ipnet", name "ipnet_stats" >>> and class "misc". >>> >> >> Is anything else using the ipnet module? >> > > I don't understand that question. Do any other kstats exist that use the module "ipnet"? >> And can we do any better than class "misc"? (Not that it's that critical >> in this >> particular case, as ipnet::ipnet_stats should be adequate to pick out the >> kstats >> of interest.) >> > > I suggest you look at the output of "kstat" and see what names are > used today. The names I chose were to be consistent with what is > already in use. I know what's used today. It's unfortunate that in most cases the kstat class hasn't been well used, with too many kstats just dumped into class misc. Which is a shame because, programmatically, filtering on the class name is pretty easy. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ _______________________________________________ networking-discuss mailing list [email protected]
