mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH *] use 64 bit jiffies
Date: Mon, 3 Feb 2003 10:28:00 +0200	[thread overview]
Message-ID: <20030203082800.GT821@mea-ext.zmailer.org> (raw)
In-Reply-To: <200302030644.h136iXs04935@Port.imtp.ilyichevsk.odessa.ua>

On Mon, Feb 03, 2003 at 08:42:59AM +0200, Denis Vlasenko wrote:
> On 3 February 2003 00:55, Tim Schmielau wrote:
> > Just a note that I have rediffed for 2.5.55 the patches that use the
> > 64 bit jiffies value to avoid uptime and process start time wrap
> > after 49.5 days. I will push them Linus-wards when he's back.
> > They can be retrieved from
....
> Wow... your patches are STILL not included??
> My 2.4 based server approaches 250 days uptime, it would be a shame
> to be unable to have uptime < 50 days with 2.5

You don't need to have 64-bit jiffy for things like internal
timers, nor for uptime tracking.

Timers have well behaving constructs to use 32-bit jiffy quite 
successfully, and 64-bit values, especially atomicish, in 32-bit 
register-poor machines (i386) are damn difficult.

I do have a number of machines with 100 to 300 day uptimes, all
with "mere" 32-bit jiffy.  With 1000 Hz clock that means at least
one full wrap-around of jiffy.

> --
> vda

/Matti Aarnio

  reply	other threads:[~2003-02-03  8:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:55 Tim Schmielau
2003-02-03  6:42 ` Denis Vlasenko
2003-02-03  8:28   ` Matti Aarnio [this message]
2003-02-03  8:47     ` Tim Schmielau
2003-02-03  8:55       ` Matti Aarnio
2003-02-04 13:00         ` Tim Schmielau
2003-02-04  6:41     ` Denis Vlasenko
2003-02-04  8:27       ` Robert de Bath
2003-02-04  8:41         ` Denis Vlasenko
2003-02-04  9:29       ` Jörn Engel
2003-02-04 13:04         ` Tim Schmielau
2003-02-17 13:55           ` Jörn Engel
2003-02-17 14:02             ` Tim Schmielau
2003-02-17 14:15             ` Matti Aarnio
2003-02-17 14:23               ` Tim Schmielau
2003-02-04 17:37       ` 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
2003-02-11 20:50       ` [patch] jiffies wrap fixes for 2.5.60 Tim Schmielau
2003-02-11 21:31         ` Roger Larsson
2003-02-12 12:09           ` Tim Schmielau
2003-02-05 11:42 ` use 64 bit jiffies broke HZ=100 case (and fix) Oleg Drokin
2003-02-05 12:22   ` Tim Schmielau

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=20030203082800.GT821@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.de \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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®