Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 2 Aug 2002 11:56:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 2 Aug 2002 11:56:37 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:24850 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Fri, 2 Aug 2002 11:56:35 -0400 Date: Fri, 2 Aug 2002 08:56:19 -0700 (PDT) From: Linus Torvalds To: Alan Cox cc: Pavel Machek , Chris Friesen , Benjamin LaHaise , Pavel Machek , Andrea Arcangeli , , Subject: Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29) In-Reply-To: <1028289587.18317.6.camel@irongate.swansea.linux.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 924 Lines: 25 On 2 Aug 2002, Alan Cox wrote: > > 2% is way too much for a lot of applications. Thats 28 minutes a day Note that _most_ PC clocks are a hell of a lot better than 2% a day, so that was really meant as the worst case for fairly broken hardware. But it apparently does happen. A more realistic schenario is less than 0.1%, but with the caveat that if the machine goes to sleep, the error goes up to infinity.. (Think of the current "jiffies" update and gettimeofday() _without_ any ntp or /etc/adjtime. For most people it is good enough to use as a wall clock. But some people literally lose or gain a minute every hour. That's the kind of drift I'm talking about). Linus - 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/