Date: Sat, 21 Aug 2010 10:10:09 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: Latest intr problems Message-ID: <4C6F7BD1.4030009@icyb.net.ua> In-Reply-To: <4C6F772A.5020703@icyb.net.ua> References: <alpine.BSF.2.00.1008201701001.19740@qbhto.arg> <4C6F772A.5020703@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
on 21/08/2010 09:50 Andriy Gapon said the following:
> on 21/08/2010 03:03 Doug Barton said the following:
>> Here are the results of a vmstat -i, the old dtrace script, and Andriy's
>> new one.
>
> I think that for such amount of data it is better to use links (perhaps a
> service like pastebin) rather than inlining it.
> BTW, it seems that there are no followups/comments on results of the old dtrace
> script, so I am not sure if there is any point in continuing to post it.
> It is useless personally for me.
>
> Back to the data.
> Could you please report results of
> procstat -k 10
> procstat -k 11
> ?
Some additional stuff.
Could you please remind what the "old dtrace script" is? :-)
Output of sysctl dev.cpu (normal and when the problem hits)
Another dtrace script:
profile:::profile-1001
{
@stacks[curthread->td_oncpu, pid, tid, stack()] = count();
}
END
{
trunc(@stacks, 20);
printa(@stacks);
}
--
Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C6F7BD1.4030009>