From: Wakko Warner <wakko@animx.eu.org>
To: bert hubert <ahu@ds9a.nl>, Olaf Fraczyk <olaf@navi.pl>,
linux-kernel@vger.kernel.org
Subject: Re: please merge 64-bit jiffy patches. Was Re: Why HZ on i386 is 100 ?
Date: Wed, 17 Apr 2002 07:09:37 -0400 [thread overview]
Message-ID: <20020417070937.A29310@animx.eu.org> (raw)
In-Reply-To: <20020416074748.GA16657@venus.local.navi.pl> <20020416233457.A1731@outpost.ds9a.nl> <20020416222156.GB20464@turbolinux.com> <20020417102828.D11817@outpost.ds9a.nl>
> > Trivially fixed with the existing 64-bit jiffies patches. As it is,
> > your uptime wraps to zero after 472 days or something like that if you
> > don't have the 64-bit jiffies patch, which is totally in the realm of
> > possibility for Linux servers.
>
> I feel your pain
>
> 4:26am up 482 days, 10:33, 2 users, load average: 0.04, 0.02, 0.00
>
> On a very remote server.
>
> So can we please merge the 64-bit jiffies patches? I sometimes think that
> that is the main reason why alpha DOES have HZ=1024 - the jiffies there
> don't wrap in an embarrassing way within two months :-)
Yes, but being that the alpha is 64-bit, it doesn't wrap at 49.7 days. I've
seen mine at 60 days or so.
--
Lab tests show that use of micro$oft causes cancer in lab animals
prev parent reply other threads:[~2002-04-17 11:06 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 7:47 Why HZ on i386 is 100 ? Olaf Fraczyk
2002-04-16 8:14 ` William Lee Irwin III
2002-04-16 8:18 ` BALBIR SINGH
2002-04-16 10:29 ` Liam Girdwood
2002-04-16 10:01 ` Olaf Fraczyk
2002-04-16 13:35 ` Terje Eggestad
2002-04-16 13:38 ` Mark Mielke
2002-04-16 13:55 ` Terje Eggestad
2002-04-16 15:32 ` Rik van Riel
2002-04-16 16:12 ` Chris Friesen
2002-04-16 17:12 ` Mark Mielke
2002-04-16 13:58 ` Alan Cox
2002-04-17 0:22 ` H. Peter Anvin
2002-04-16 16:27 ` Linus Torvalds
2002-04-16 16:50 ` David Mosberger
2002-04-16 17:18 ` Davide Libenzi
2002-04-16 17:52 ` David Mosberger
2002-04-16 18:10 ` Davide Libenzi
2002-04-17 0:49 ` David Mosberger
2002-04-17 0:57 ` Robert Love
2002-04-17 1:07 ` Davide Libenzi
2002-04-17 5:18 ` Mark Mielke
2002-04-17 5:34 ` Linus Torvalds
2002-04-17 6:01 ` Robert Love
2002-04-17 6:17 ` David Mosberger
2002-04-17 7:59 ` arjan
2002-04-17 8:04 ` Matti Aarnio
2002-04-23 22:42 ` Albert D. Cahalan
2002-04-17 10:12 ` Martin Dalecki
2002-04-18 1:51 ` Dan Mann
2002-04-17 1:22 ` Davide Libenzi
2002-04-17 3:19 ` Ben Greear
2002-04-17 7:55 ` Helge Hafting
2002-04-21 18:00 ` Pavel Machek
2002-04-22 17:20 ` John Alvord
2002-04-22 21:52 ` george anzinger
2002-04-22 23:06 ` J.D. Bakker
2002-04-22 23:26 ` Anton Blanchard
2002-04-23 19:03 ` george anzinger
2002-04-23 7:08 ` Alan Cox
2002-04-22 17:24 ` David Mosberger
2002-04-16 12:42 ` Richard B. Johnson
2002-04-16 12:31 ` Richard B. Johnson
2002-04-16 14:04 ` Bill Davidsen
2002-04-16 21:34 ` bert hubert
2002-04-16 22:21 ` Andreas Dilger
2002-04-16 22:37 ` Herbert Xu
2002-04-16 22:56 ` Andreas Dilger
2002-04-17 0:34 ` J. Dow
2002-04-17 2:40 ` Herbert Xu
2002-04-17 12:44 ` Kent Borg
2002-04-17 8:28 ` please merge 64-bit jiffy patches. Was " bert hubert
2002-04-17 11:05 ` please merge 64-bit jiffy patches Tim Schmielau
2002-04-17 11:12 ` bert hubert
2002-04-17 12:33 ` Bill Davidsen
2002-04-17 12:42 ` bert hubert
2002-04-17 14:57 ` Bill Davidsen
2002-04-17 11:09 ` Wakko Warner [this message]
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=20020417070937.A29310@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@navi.pl \
/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