Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262487AbVESNZs (ORCPT ); Thu, 19 May 2005 09:25:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262492AbVESNZs (ORCPT ); Thu, 19 May 2005 09:25:48 -0400 Received: from users.ccur.com ([208.248.32.211]:24697 "EHLO gamx.iccur.com") by vger.kernel.org with ESMTP id S262487AbVESNZm (ORCPT ); Thu, 19 May 2005 09:25:42 -0400 Date: Thu, 19 May 2005 09:24:57 -0400 From: Joe Korty To: Andi Kleen Cc: robustmutexes@lists.osdl.org, george@mvista.com, linux-kernel@vger.kernel.org Subject: Re: [RFC] A more general timeout specification Message-ID: <20050519132457.GA9357@tsunami.ccur.com> Reply-To: joe.korty@ccur.com References: <20050518201517.GA16193@tsunami.ccur.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: 1004 Lines: 24 On Thu, May 19, 2005 at 01:49:11AM +0200, Andi Kleen wrote: > Joe Korty writes: > > > The fusyn (robust mutexes) project proposes the creation > > of a more general data structure, 'struct timeout', for the > > specification of timeouts in new services. In this structure, > > the user specifies: > > > > a time, in timespec format. > > the clock the time is specified against (eg, CLOCK_MONOTONIC). > > whether the time is absolute, or relative to 'now'. > > If you do a new structure for this I would suggest adding a > "precision" field (or the same with a different name). Basically > precision would tell the kernel that the wakeup can be in a time > range, not necessarily on the exact time specified. Very cool. 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/