Joachim Worringen stated:
> Sean McGrath wrote:
>> libkstat and libdtrace.
>>
>> The majority of system statistics etc are/can be gleamed from libkstat
>> eg mpstat, iostat and vmstat make use of libkstat.
>> Theres intrstat which uses the dtrace library.
>> For network theres Tim Cook's nicstat from his blog blogs.sun.com/timc
>> which also uses libkstat...
>>
>> The source for all these can be viewed at src.opensolaris.org for examples
>> on how to use them. Though the nicstat source is just from Tim's blog.
>
> Thanks for the hint - it also lead me to
> http://developers.sun.com/solaris/articles/kstatc.html.
Ya, I knew about that article but couldn't find the link :)
>
>> Theres a few blogs on howto use libkstat..
>> I find it easier to use libkstat then on linux where having to open
>> various /proc/* files and parse each files own format..
>> (unless theres a libproc on linux to do all this I don't know)
>
> Of course, an interface like libkstat is much nicer than parsing hardly
> documented files from /proc that differ from version to version and
> platform to platform! It just happens to work for our purpose.
>
>> Even then dtrace can help, look at how to add your own dtrace probes to
>> your application ?
>
> I figure I'd rather add dtrace probes to our drivers to be read from the
> benchmark via libdtrace!?
Its a similar thing. The kernel source for solaris (src.opensolaris.org)
has plently of drivers using dtrace probes for examples.
Though if your drivers are i/o based then the io dtrace provider may
be worth a look. Could save some coding..
Regards,
Sean.
.
>
> Joachim
>
> --
> Joachim Worringen, Software Architect, Dolphin Interconnect Solutions
> phone ++49/(0)228/324 08 17 - http://www.dolphinics.com
--
Sean.
.
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
