Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 1 Aug 2002 15:14:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 1 Aug 2002 15:14:57 -0400 Received: from tapu.f00f.org ([66.60.186.129]:20150 "EHLO tapu.f00f.org") by vger.kernel.org with ESMTP id ; Thu, 1 Aug 2002 15:14:55 -0400 Date: Thu, 1 Aug 2002 12:18:24 -0700 From: Chris Wedgwood To: Linus Torvalds Cc: Alan Cox , Chris Friesen , Benjamin LaHaise , Pavel Machek , Andrea Arcangeli , linux-kernel@vger.kernel.org, linux-aio@kvack.org Subject: Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29) Message-ID: <20020801191823.GA24428@tapu.f00f.org> References: <1028223041.14865.80.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1021 Lines: 30 On Thu, Aug 01, 2002 at 09:30:04AM -0700, Linus Torvalds wrote: A 2% error may not be a big problem for most people, of course. But it might be a huge problem for others. Those people would have to do their own re-calibration.. How about export the value via a syscall and also export an 'error' which for now could just be set to 5% or something conservative and refined later if necessary or cleanup on other architectures, something like: /* export monotonically increasing nanoseconds since boot to user-space. kt_time is a relative value, it does NOT necessarily imply nanoseconds since boot. kt_err should be greater than 1stdev of the error in kt_time */ struct kern_time { __u64 kt_ns; __u64 kt_err; }; --cw - 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/