From: Andi Kleen <ak@suse.de>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org, tim@physik3.uni-rostock.de
Subject: Re: [PATCH] make jiffies wrap 5 min after boot
Date: 16 Feb 2003 07:36:26 +0100 [thread overview]
Message-ID: <p73znowybo5.fsf@amdsimf.suse.de> (raw)
In-Reply-To: Anton Blanchard's message of "16 Feb 2003 03:11:30 +0100"
Anton Blanchard <anton@samba.org> writes:
> Hi,
>
> > +#define INITIAL_JIFFIES (0xffffffffUL & (unsigned long)(-300*HZ))
>
> In order to make 64bit arches wrap too, you might want to use -1UL here.
> Not that jiffies should wrap on a 64bit machine...
Seems somewhat pointless.
(2^64-1) / (1000 * 3600 * 24 * 365)
~584942417.35507203243911719939
I doubt any system ever will have an uptime of > 584 million years
(assuming HZ=1000) and if jiffies wrap will be the least of their
problems.
-Andi
next parent reply other threads:[~2003-02-16 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L2.0302040935230.6174-100000@dragon.pdx.osdl.net.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0302160232120.7975-100000@gans.physik3.uni-rostock.de.suse.lists.linux.kernel>
[not found] ` <20030216020808.GF9833@krispykreme.suse.lists.linux.kernel>
2003-02-16 6:36 ` Andi Kleen [this message]
2003-02-16 6:56 ` [PATCH] make jiffies wrap 5 min after boot Andrew Morton
2003-02-16 7:00 ` Andi Kleen
2003-02-16 8:10 ` Tim Schmielau
2003-02-04 17:37 [PATCH *] use 64 bit jiffies Randy.Dunlap
2003-02-16 1:37 ` [PATCH] make jiffies wrap 5 min after boot Tim Schmielau
2003-02-16 2:08 ` Anton Blanchard
2003-02-16 2:43 ` William Lee Irwin III
2003-02-16 2:50 ` Michael Vergoz
2003-02-16 6:37 ` Robert Love
2003-02-16 7:16 ` Muli Ben-Yehuda
2003-02-16 11:50 ` Falk Hueffner
2003-02-16 12:04 ` William Lee Irwin III
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=p73znowybo5.fsf@amdsimf.suse.de \
--to=ak@suse.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
/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