Quoting David Christensen (from Thu, 5 May 2011
13:08:56 -0700):
I was looking at using dtrace to help characterize performance
for the new bxe(4) driver but I'm having problems with the very
simple task of capturing time spent in a function. The D script
I'm using looks like the following:
On Thu, May 5, 2011 at 1:08 PM, David Christensen wrote:
> I was looking at using dtrace to help characterize performance
> for the new bxe(4) driver but I'm having problems with the very
> simple task of capturing time spent in a function. The D script
> I'm using looks like the following:
>
> #
On Thu, May 5, 2011 at 4:33 PM, David Christensen wrote:
>> > After building dtrace into the kernel and loading the dtraceall
>> > kernel module, when I load my bxe kernel module and run "dtrace -l"
>> > to list all supported probes I notice that many functions have an
>> > entry probe but no exit
> > After building dtrace into the kernel and loading the dtraceall
> > kernel module, when I load my bxe kernel module and run "dtrace -l"
> > to list all supported probes I notice that many functions have an
> > entry probe but no exit probe. This effectively prevents me from
> > calculating tim
I was looking at using dtrace to help characterize performance
for the new bxe(4) driver but I'm having problems with the very
simple task of capturing time spent in a function. The D script
I'm using looks like the following:
#pragma D option quiet
fbt:if_bxe::entry
{
self->in = timesta
