From owner-cvs-all Sun Nov 25 19:42:56 2001 Delivered-To: cvs-all@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id E8A8E37B417; Sun, 25 Nov 2001 19:42:52 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.5/8.11.5) with ESMTP id fAQ3gpY40667; Sun, 25 Nov 2001 20:42:52 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200111260342.fAQ3gpY40667@aslan.scsiguy.com> To: Peter Wemm Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern tty.c In-Reply-To: Your message of "Fri, 16 Nov 2001 16:26:57 PST." <200111170026.fAH0QvX25570@freefall.freebsd.org> Date: Sun, 25 Nov 2001 20:42:51 -0700 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >peter 2001/11/16 16:26:57 PST > > Modified files: > sys/kern tty.c > Log: > utime/stime.tv_sec are elapsed times, not relative to 1970. We can > safely print them as longs. Even if ^T overflows after a process > has accumulated 68 years of user or system time, it is no big deal. I wonder if this will be such a safe assumption when we're running on highly parallel machines? Even on just a 16 CPU box, you'd only need 4.25 years of wallclock time to see an overflow. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message