One more thing. On the T1000, I run this script:
#!/usr/sbin/dtrace -s
profile-997
/arg1 && execname == "ssh"/
{
@[execname,pid,ustack()]=count()
}
profile-997
/arg1 && execname == "sshd"/
{
@[execname,pid,ustack()]=count()
}
profile-50s
{
exit(0);
}
END
{
trunc(@,1000)
}
and I get a whole bunch of errors that look like this:
dtrace: error on enabled probe ID 1 (ID 1853: profile:::profile-997):
invalid address (0x3bb98000) in action #4
The only difference on these is that the address is different each
time. I don't get these message on the v220 at all. Any ideas what the
problem is?
Brian Utterback wrote:
> I have been doing some profiling using the profile provider. I have a
> command that runs more slowly on the T1000 than it does on prior
> systems and I am trying to find out why. Using the profile provider at
> 1000 hz, and aggregating on the ustack output, I find that the same
> function appears at the top of the stack on both platforms, but on
> each there are specific instruction locations within the function that
> appear most often and these are different on the two platforms. They
> are consistent on a platform. That is when I re-run the test on one
> platform, about 4 specific PC locations will appear in the top spots,
> but on that platform it is always the same 4 and the 4 are different
> between the platforms.
>
> So, I am trying to figure out whether or not there is something
> special happening at those locations, or just before or just after, or
> are they just artifacts of how the profile provider works? There are
> two function calls with this function, but neither set of 4 locations
> seem to be near the calls. And if the time was really spent inside the
> next lower down level, wouldn't that have been reflected in the ustack
> output?
--
blu
There are two rules in life:
Rule 1- Don't tell people everything you know
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
_______________________________________________
dtrace-discuss mailing list
[email protected]
