Date: Tue, 22 Jan 2008 19:42:25 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Stefan Lambrev <stefan.lambrev@moneybookers.com> Cc: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no>, freebsd-hackers@FreeBSD.org Subject: Re: gettimeofday() in hping Message-ID: <47963911.4000002@FreeBSD.org> In-Reply-To: <4796357B.9020508@moneybookers.com> References: <4795CC13.7080601@moneybookers.com> <868x2i3v8d.fsf@ds4.des.no> <864pd63v2h.fsf@ds4.des.no> <4795FE54.9090606@moneybookers.com> <86lk6i0vzk.fsf@ds4.des.no> <479605E2.6070709@moneybookers.com> <479621BE.2060907@FreeBSD.org> <4796357B.9020508@moneybookers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Lambrev wrote: >> You should use hwpmc to verify where the application is really >> spending time, since gettimeofday doesn't seem to account for it all. > pmc: Unknown Intel CPU. > module_register_init: MOD_LOAD (hwpmc, 0xffffffff8029906d, > 0xffffffff8054c500) error 78 OK, this is the famous problem with modern CPUs that jkoshy has declined to work around :( There are patches for this in perforce, see http://perforce.freebsd.org/changeView.cgi?CH=126189 > What was the other way to do this profiling? No other that I have found to be useful. > Can ktrace help? Not really, it only tells you what syscalls were made. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47963911.4000002>