Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965161AbVIAOdW (ORCPT ); Thu, 1 Sep 2005 10:33:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965148AbVIAOdW (ORCPT ); Thu, 1 Sep 2005 10:33:22 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:42373 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S965161AbVIAOdV (ORCPT ); Thu, 1 Sep 2005 10:33:21 -0400 Date: Thu, 1 Sep 2005 16:32:49 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Joe Korty cc: "Perez-Gonzalez, Inaky" , akpm@osdl.org, george@mvista.com, johnstul@us.ibm.com, linux-kernel@vger.kernel.org Subject: Re: FW: [RFC] A more general timeout specification In-Reply-To: <20050901135049.GB1753@tsunami.ccur.com> Message-ID: References: <20050901135049.GB1753@tsunami.ccur.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: 692 Lines: 20 Hi, On Thu, 1 Sep 2005, Joe Korty wrote: > > When you convert a user time to kernel time you can > > automatically validate > > Kernel time sucks. It is just a single clock, it may not have > the attributes of the clock that the user really wished to use. Wrong. The kernel time is simple and effective for almost all users. We are talking about _timeouts_ here, what fancy "attributes" does that need that are just not overkill? 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/