From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [2.4] Are jiffies in jiffies?
Date: Tue, 04 Nov 2003 13:36:10 +0100 [thread overview]
Message-ID: <3FA79D3A.8090308@softhome.net> (raw)
Hello!
[ I beleive this is real FAQ - so responding with private e-mails
more appropriate.
ptr("RTFM") != 0 are welcome. ]
jiffies declared in kernel/timer.c.
Name suggests that it is incremented 100 times per second.
LDD2 suggests that it is incremented every 1000/HZ per second.
Is it just name misleading - or I really miss the point?
So to translate this to seconds i need (jiffies*1000/HZ)
and milliseconds are just (jiffies/HZ) then.
Am I right?
I need this for {add,mod}_timer() calls.
--
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
"... and for $64000 question, could you get yourself |_|*|_|
vaguely familiar with the notion of on-topic posting?" |_|_|*|
-- Al Viro @ LKML |*|*|*|
next reply other threads:[~2003-11-04 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 12:36 Ihar 'Philips' Filipau [this message]
2003-11-04 12:52 ` [2.4] Are jiffies in jiffies? Tomas Telensky
2003-11-04 13:04 ` Bernd Petrovitsch
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=3FA79D3A.8090308@softhome.net \
--to=filia@softhome.net \
--cc=linux-kernel@vger.kernel.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).