From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kprof
Date: Sun, 21 Apr 2002 12:53:03 -0400 [thread overview]
Message-ID: <b82974fc62461036edf714574f008567@plan9.bell-labs.com> (raw)
_kproftimer is called from the clock routine.
You're proposing the gprof approach, where you notice 12% of the time
is spent in a routine, which is called in 3 places, so each place gets
charged 4%. Chances are against you that this way of accounting will
give you the correct answer.
-rob
next reply other threads:[~2002-04-21 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 16:53 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-21 20:35 andrey mirtchovski
2002-04-21 19:13 forsyth
2002-04-21 16:51 andrey mirtchovski
2002-04-21 16:41 rob pike, esq.
2002-04-21 16:30 andrey mirtchovski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b82974fc62461036edf714574f008567@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).