From: Chris Friesen <cfriesen@nortel.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Russell King <rmk+lkml@arm.linux.org.uk>,
jdavis@accessline.com, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
Date: Thu, 21 Apr 2005 09:53:32 -0600 [thread overview]
Message-ID: <4267CC7C.10907@nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504210752560.2344@ppc970.osdl.org>
Linus Torvalds wrote:
> If you calculate the expected timeout from the time-of-day in the caller,
> your drift not only goes away, but you'll actually be able to handle
> things like "oops, the machine is under load so I missed an event".
Does mainline have a high precision monotonic wallclock that is not
affected by time-of-day changes? Something like "nano/mico seconds
since boot"?
Chris
next prev parent reply other threads:[~2005-04-21 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 17:39 Odd Timer behavior in 2.6 vs 2.4 (1 extra tick) jdavis
2005-04-08 22:19 ` Steven Rostedt
2005-04-21 2:58 ` [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)] Steven Rostedt
2005-04-21 3:40 ` Steven Rostedt
2005-04-21 8:51 ` Russell King
2005-04-21 10:51 ` Steven Rostedt
2005-04-21 14:58 ` Linus Torvalds
2005-04-21 15:34 ` Steven Rostedt
2005-04-21 15:53 ` Chris Friesen [this message]
2005-04-21 16:13 ` Linus Torvalds
2005-04-22 2:54 ` Edgar Toernig
2005-04-29 21:28 ` Odd Timer behavior in 2.6 vs 2.4 (1 extra tick) Nish Aravamudan
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=4267CC7C.10907@nortel.com \
--to=cfriesen@nortel.com \
--cc=akpm@osdl.org \
--cc=jdavis@accessline.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.