From: 914059751@qq.com (胡杨树)
To: linux-arm-kernel@lists.infradead.org
Subject: Query about loops_per_jiffy
Date: Tue, 19 Jan 2010 15:42:53 +0800 [thread overview]
Message-ID: <tencent_5CA6CD330328846756327199@qq.com> (raw)
Hi, oldhands:)
I have a question about how loops_per_jiffy converted to BogoMips,
loops_per_jiffy * HZ <----------- that's number of instructions CPU executes in a second
BogoMips <-------------------------- Millions of instructions CPU executes in a second
so , do the math!
(loops_per_jiffy * HZ)/1000,000 will give a BogoMips value.
then why calibrate_delay do it like the following:
printk(KERN_CONT "%lu.%02lu BogoMIPS (lpj=%lu)\n",
loops_per_jiffy/(500000/HZ),
(loops_per_jiffy/(5000/HZ)) % 100, loops_per_jiffy);
Am I missing something ?
Great thanks for any tips!
next reply other threads:[~2010-01-19 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 7:42 胡杨树 [this message]
2010-01-19 8:21 ` Query about loops_per_jiffy Alessandro Rubini
2010-01-19 8:22 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 13:38 胡杨树
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=tencent_5CA6CD330328846756327199@qq.com \
--to=914059751@qq.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).