On Sun, 26 Dec 2004, Robert Watson wrote: > > On Sat, 25 Dec 2004, Jeff Roberson wrote: > > > To use the tool, you will need to define KTR_SCHED in KTR_COMPILE and > > KTR_MASK. I'd also bump entires up to 32768 or larger so you can grab a > > few seconds of data. Run your workload, and then capture the data with > > 'ktrdump -ct > ktr.out'. Then you simply run python schedgraph.py > > ktr.out. This requires a recent version of python and > > ports/x11-toolkits/py-tkinter. > > Great! > > For those who need a little more hand-holding getting KTR running, here's > a URL to try: > > http://www.watson.org/~robert/freebsd/netperf/ktr/ > > It's been my hope people would start producing more post-processing tools > -- KTR can collect some really great data that's just sitting there > waiting to be mined. I'd be interested in seeing post-processing tools > for locking as well. This looks like a great tool that will be really > helpful in understanding behavior and performance. Well, if you want to display contention, you can filter on that using the configuration menu, and display only contested locks. This tool could be easily extended to add events for picking up and droping mutexes as well. It would only require a new KTR and a regexp to match it. > > Thanks! > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert_at_fledge.watson.org Principal Research Scientist, McAfee Research > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Sun Dec 26 2004 - 17:17:45 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:25 UTC