From: Tim Walberg <twalberg@mindspring.com>
To: george anzinger <george@mvista.com>
Cc: Jonathan Briggs <zlynx@acm.org>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nasty suprise with uptime
Date: Tue, 30 Oct 2001 07:50:43 -0600 [thread overview]
Message-ID: <20011030075043.B4904@mindspring.com> (raw)
In-Reply-To: <E15yJD1-0003uO-00@the-village.bc.nu> <3BDDBE89.397E42C0@lexus.com> <20011029124753.F21285@one-eyed-alien.net> <4.3.2.7.2.20011029172525.00bb2270@mail.osagesoftware.com> <3BDDE642.8000901@acm.org> <3BDE6A80.3A68A44E@mvista.com>
In-Reply-To: <3BDE6A80.3A68A44E@mvista.com> from george anzinger on 10/30/2001 02:53
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
Wouldn't it be fairly simple for the kernel to just remember the (wall
clock) time at boot, and uptime just subtract that from the current
(wall clock) time? It would be another variable in the kernel requiring
storage but not having a whole lot of use, but what's another 8 bytes
these days? (ok, maybe it would be more critical in embedded and other
such space critical applications, but not for general desktop/server
use...)
tw
On 10/30/2001 00:53 -0800, george anzinger wrote:
>> Jonathan Briggs wrote:
>> >
>> > A 32 bit uptime patch should also include a new kernel parameter that
>> > could be passed from LILO: uptime. Then you could test the uptime patch
>> > by passing uptime=4294967295
>> >
>> > Or make /proc/uptime writable.
>>
>> NO NO NO!
>>
>> First uptime is a conversion of jiffies. Second, the POSIX standard
>> wants a CLOCK_MONOTONIC which, by definition, can not be set. Jiffies
>> is the most reasonable source for this clock. I am afraid you will have
>> to accumulate "real" time for uptime :)
>>
>> George
>>
>>
>> >
>> > David Relson wrote:
>> >
>> > > Let's assume you have the counter changed to 32 bits - RIGHT NOW
>> > > (tm). Build a kernel, install it, reboot. It'll be over a year
>> > > (approx Jan 2003) before the change will be noticeable...
>> > >
>> > > Methinks that's a long time to wait for a result :-)
>> > >
>> > > David
>> > >
>> >
>> > -
>> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> > the body of a message to majordomo@vger.kernel.org
>> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>> > Please read the FAQ at http://www.tux.org/lkml/
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
End of included message
--
twalberg@mindspring.com
[-- Attachment #2: Type: application/pgp-signature, Size: 175 bytes --]
next prev parent reply other threads:[~2001-10-30 13:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 20:31 Nasty suprise with uptime J Sloan
2001-10-29 20:40 ` Alan Cox
2001-10-29 20:39 ` J Sloan
2001-10-29 20:47 ` Matthew Dharm
2001-10-29 20:52 ` J Sloan
2001-11-09 0:45 ` Dr. Kelsey Hudson
2001-10-29 21:26 ` David Relson
2001-10-29 23:29 ` Jonathan Briggs
2001-10-30 8:53 ` george anzinger
2001-10-30 13:50 ` Tim Walberg [this message]
2001-10-30 14:47 ` GOMBAS Gabor
2001-10-30 15:39 ` Tim Walberg
2001-10-30 16:18 ` GOMBAS Gabor
2001-10-30 22:53 ` Mike Castle
2001-10-30 8:20 ` george anzinger
2001-10-30 9:47 ` bert hubert
2001-10-30 10:37 ` Mike Fedyk
2001-10-30 15:56 ` Chris Meadors
2001-10-30 16:22 ` Laurent de Segur
2001-10-30 21:53 ` [OT] " J Sloan
2001-10-30 22:52 ` Jan Dvorak
2001-10-30 23:25 ` [OT] " J Sloan
2001-10-30 7:46 ` Neale Banks
2001-10-30 7:46 ` Mike Fedyk
2001-10-30 8:15 ` Ville Herva
2001-10-30 8:22 ` Ville Herva
2001-10-30 8:36 ` J. Dow
2001-10-30 9:33 ` Alan Cox
2001-10-30 16:25 ` Matt Bernstein
2001-10-30 19:43 ` Oden Eriksson
2001-10-29 23:10 ` Mike Fedyk
2001-10-29 23:20 ` J Sloan
2001-10-29 23:28 ` Mike Fedyk
2001-10-30 8:21 ` Ville Herva
2001-10-31 22:36 ` J Sloan
2001-11-01 0:49 ` Gerhard Mack
2001-10-30 8:49 ` george anzinger
2001-10-30 18:17 ` J Sloan
2001-10-30 9:06 ` Alan Cox
2001-10-30 19:19 ` J Sloan
-- strict thread matches above, loose matches on Subject: below --
2001-10-30 16:35 Jesse Pollard
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=20011030075043.B4904@mindspring.com \
--to=twalberg@mindspring.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zlynx@acm.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