Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965135AbVIANyF (ORCPT ); Thu, 1 Sep 2005 09:54:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965134AbVIANyD (ORCPT ); Thu, 1 Sep 2005 09:54:03 -0400 Received: from users.ccur.com ([208.248.32.211]:40382 "EHLO gamx.iccur.com") by vger.kernel.org with ESMTP id S965118AbVIANyA (ORCPT ); Thu, 1 Sep 2005 09:54:00 -0400 Date: Thu, 1 Sep 2005 09:53:11 -0400 From: Joe Korty To: Roman Zippel Cc: Daniel Walker , "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 Message-ID: <20050901135311.GC1753@tsunami.ccur.com> Reply-To: joe.korty@ccur.com References: <1125533289.15034.64.camel@dhcp153.mvista.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 697 Lines: 15 On Thu, Sep 01, 2005 at 11:22:32AM +0200, Roman Zippel wrote: > 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. Struct timeout is just a struct timespec + a bit for absolute/relative + a field for clock specification. What's so complex about that? It captures everything needed to specify time, from here to the end of time. Joe - 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/