From: Jon Masters <jonmasters@gmail.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: Henry Margies <henry.margies@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: Is there a problem in timeval_to_jiffies?
Date: Wed, 29 Sep 2004 22:24:08 +0100 [thread overview]
Message-ID: <35fb2e5904092914243694baa4@mail.gmail.com> (raw)
In-Reply-To: <415B2178.7060907@am.sony.com>
On Wed, 29 Sep 2004 13:56:24 -0700, Tim Bird <tim.bird@am.sony.com> wrote:
Apologies for butting in.
> If you are rescheduling one-shot timers immediately
> after they fire, you should 'undershoot' on the time
> interval, to hit the tick boundary you want, based
> on the jiffy resolution of your platform.
Can I just do a ^^^^ here - this is what the original poster really
needs to know to solve the immediate problem of overshooting - then a
good book can help with the rest.
Jon.
next prev parent reply other threads:[~2004-09-29 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 13:48 Is there a problem in timeval_to_jiffies? Henry Margies
2004-09-12 14:33 ` Henry Margies
2004-09-16 3:30 ` Randy.Dunlap
2004-09-16 9:54 ` George Anzinger
2004-09-16 15:38 ` Henry Margies
2004-09-16 18:10 ` Henry Margies
[not found] ` <20040916200203.6259e113.henry.margies@gmx.de>
2004-09-16 20:19 ` George Anzinger
2004-09-17 9:55 ` Henry Margies
2004-09-29 20:56 ` Tim Bird
2004-09-29 21:24 ` Jon Masters [this message]
2004-10-01 11:42 ` Henry Margies
[not found] <2CxDn-2ib-51@gated-at.bofh.it>
[not found] ` <2DDGs-7Om-31@gated-at.bofh.it>
[not found] ` <2EVhQ-6Qe-5@gated-at.bofh.it>
[not found] ` <2F1e7-2r9-21@gated-at.bofh.it>
[not found] ` <2Fb3o-1cT-27@gated-at.bofh.it>
[not found] ` <2Fb3o-1cT-25@gated-at.bofh.it>
[not found] ` <2FnQM-1wt-1@gated-at.bofh.it>
[not found] ` <2JTS7-5Ri-3@gated-at.bofh.it>
2004-09-29 22:03 ` Andi Kleen
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=35fb2e5904092914243694baa4@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=henry.margies@gmx.de \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
/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.