Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030187AbVIAPLZ (ORCPT ); Thu, 1 Sep 2005 11:11:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030191AbVIAPLZ (ORCPT ); Thu, 1 Sep 2005 11:11:25 -0400 Received: from gateway-1237.mvista.com ([12.44.186.158]:23537 "EHLO av.mvista.com") by vger.kernel.org with ESMTP id S932249AbVIAPLV (ORCPT ); Thu, 1 Sep 2005 11:11:21 -0400 Subject: Re: FW: [RFC] A more general timeout specification From: Daniel Walker To: Roman Zippel Cc: Joe Korty , "Perez-Gonzalez, Inaky" , akpm@osdl.org, george@mvista.com, johnstul@us.ibm.com, linux-kernel@vger.kernel.org In-Reply-To: References: <20050901135049.GB1753@tsunami.ccur.com> Content-Type: text/plain Date: Thu, 01 Sep 2005 08:11:08 -0700 Message-Id: <1125587468.32005.12.camel@c-67-188-6-232.hsd1.ca.comcast.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-6) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 797 Lines: 24 On Thu, 2005-09-01 at 16:32 +0200, Roman Zippel wrote: > 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? Or rather, posix timers ? Daniel - 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/