Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750886AbVIAJWx (ORCPT ); Thu, 1 Sep 2005 05:22:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750914AbVIAJWx (ORCPT ); Thu, 1 Sep 2005 05:22:53 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:64899 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S1750886AbVIAJWw (ORCPT ); Thu, 1 Sep 2005 05:22:52 -0400 Date: Thu, 1 Sep 2005 11:22:32 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Daniel Walker cc: "Perez-Gonzalez, Inaky" , akpm@osdl.org, joe.korty@ccur.com, george@mvista.com, johnstul@us.ibm.com, linux-kernel@vger.kernel.org Subject: RE: FW: [RFC] A more general timeout specification In-Reply-To: <1125533289.15034.64.camel@dhcp153.mvista.com> Message-ID: References: <1125533289.15034.64.camel@dhcp153.mvista.com> 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: 837 Lines: 21 Hi, On Wed, 31 Aug 2005, Daniel Walker wrote: > > What "more versions" are you talking about? When you convert a user time > > to kernel time you can automatically validate it and later you can use > > standard kernel APIs, so you don't have to add even more API bloat. > > What's kernel time? Are you talking about jiffies? The whole point of > multiple clocks is to allow for different degrees of precision. For a timeout? Please get real. If you need more precision, use a dedicated timer API, but don't make the general case more complex for the 99.99% of other users. bye, Roman - 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/