mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Frazer <mark@somanetworks.com>
To: liste noyau linux <linux-kernel@vger.kernel.org>
Subject: Re: [timer] max timeout
Date: Fri, 25 May 2001 17:26:28 -0400	[thread overview]
Message-ID: <20010525172628.P32217@somanetworks.com> (raw)
In-Reply-To: <20010523162801.38dabdff.sebastien.person@sycomore.fr> <3B0EC786.D7B65706@mvista.com>
In-Reply-To: <3B0EC786.D7B65706@mvista.com>; from george@mvista.com on Fri, May 25, 2001 at 01:58:46PM -0700

george anzinger <george@mvista.com> [01/05/25 17:04]:
> More than enough on the fp.  Now the other question.  
> 
> The time value is in jiffies (aka 1/Hz sec.).  The max value (in a 32
> bit system) is 0x7ffffff.  This value is added to the current value of
> jiffies to get the the absolute timer expire time.  While the value is
> unsigned (and thus you could go higher) the compare code (timer_before()
> and timer_after()) depend on the subtraction (of jiffies from expire) to
> be of the correct sign.  To insure this you must keep the timeout values
> sign clear (or if you don't like to think of an unsigned as having a
> sign, then the highest order bit must be zero).
> 
> George

The output of `find . -type f | xargs grep 'jiffies +'` would suggest
that there are a few latent bugs as jiffies grows to values near the
top of its range.  I guess this hasn't turned up as 0x7fffffff / (100 *
3600 * 24) = 248.55.



  reply	other threads:[~2001-05-25 21:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23 14:28 sebastien person
2001-05-23 14:38 ` Andi Kleen
2001-05-23 14:58 ` Andrzej Krzysztofowicz
2001-05-25  8:24 ` sebastien person
2001-05-25 20:58 ` george anzinger
2001-05-25 21:26   ` Mark Frazer [this message]
2001-05-25 21:45     ` Horst von Brand

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=20010525172628.P32217@somanetworks.com \
    --to=mark@somanetworks.com \
    --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

all inboxes | Powered by JetHome®