public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <joe@tmsusa.com>
To: bert hubert <ahu@ds9a.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: jiffies rollover, uptime etc.
Date: Mon, 18 Feb 2002 15:56:29 -0800	[thread overview]
Message-ID: <3C7194AD.2050805@tmsusa.com> (raw)
In-Reply-To: <3C717DEA.7090309@candelatech.com> <E16cwUx-00073d-00@the-village.bc.nu> <20020219002614.A27210@outpost.ds9a.nl>

FWIW our servers that wrapped around
almost 4 months ago have been running
fine, no real problems - Red Hat 6.1 with
2.2.17-pre4 kernel.

Joe

bert hubert wrote:

>On Mon, Feb 18, 2002 at 10:31:34PM +0000, Alan Cox wrote:
>
>>>I wonder, is it more expensive to write all drivers to handle the
>>>wraps than to take the long long increment hit?  The increment is
>>>
>>Total cost of handling it right - 0 clocks. Its simply about maths order
>>and sign 
>>
>
>$ uname -a ; uptime
>Linux newyork-1 2.2.18 #3 Mon Dec 11 15:57:33 EST 2000 i686 unknown
>  6:22pm  up 425 days,  1:35,  3 users,  load average: 0.10, 0.05, 0.01
>
>This server is pretty remote and hard to reach, and not sure to reboot
>properly unattended - are there predictions about how well 2.2.18 will
>survive jiffy wraparound?
>
>Would you consider it worth rebooting for? By the way, this is our second
>most important production server, I'm exceedingly pleased with the
>stability. We've abused it no end.
>
>Thanks.
>
>Regards,
>
>bert
>



  reply	other threads:[~2002-02-18 23:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18 21:42 jiffies rollover, uptime etc Oliver Hillmann
2002-02-18 22:10 ` Alan Cox
2002-02-18 22:03   ` Oliver Hillmann
2002-02-18 22:19   ` Ben Greear
2002-02-18 22:32     ` Tim Schmielau
2002-02-18 22:43     ` Alan Cox
2002-02-18 23:26       ` bert hubert
2002-02-18 23:56         ` J Sloan [this message]
2002-02-18 23:57         ` Alan Cox
2002-02-19  0:58         ` Stephen Frost
2002-02-19  4:47           ` Paul Jakma
2002-02-19  0:17     ` Bill Davidsen
2002-02-19 20:55       ` george anzinger
2002-02-20 11:36         ` Ville Herva
2002-02-20 17:20           ` Mike Fedyk
2002-02-20 17:24             ` Rik van Riel
2002-02-20 17:32               ` Mike Fedyk
2002-02-20 17:39                 ` Rik van Riel
2002-02-20 17:44                   ` Mike Fedyk
2002-02-20 17:56                 ` Derek Gladding
2002-02-21 13:19                 ` Bill Davidsen
2002-02-20 19:08               ` David Mosberger
2002-02-20 19:53               ` Robert Love
2002-02-20 15:46         ` Bill Davidsen
2002-02-20 16:50           ` george anzinger
2002-02-18 22:12 ` Tim Schmielau
2002-02-18 23:22   ` J Sloan
  -- strict thread matches above, loose matches on Subject: below --
2002-02-19  2:54 Chris Adams

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=3C7194AD.2050805@tmsusa.com \
    --to=joe@tmsusa.com \
    --cc=ahu@ds9a.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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