From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964911AbVHaXGw (ORCPT ); Wed, 31 Aug 2005 19:06:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964940AbVHaXGv (ORCPT ); Wed, 31 Aug 2005 19:06:51 -0400 Received: from zctfs063.nortelnetworks.com ([47.164.128.120]:26810 "EHLO zctfs063.nortelnetworks.com") by vger.kernel.org with ESMTP id S964911AbVHaXGv (ORCPT ); Wed, 31 Aug 2005 19:06:51 -0400 Message-ID: <431637EF.10803@nortel.com> Date: Wed, 31 Aug 2005 17:06:23 -0600 From: "Christopher Friesen" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Perez-Gonzalez, Inaky" CC: joe.korty@ccur.com, akpm@osdl.org, george@mvista.com, johnstul@us.ibm.com, linux-kernel@vger.kernel.org Subject: Re: FW: [RFC] A more general timeout specification References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 31 Aug 2005 23:06:24.0996 (UTC) FILETIME=[9C391240:01C5AE80] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Perez-Gonzalez, Inaky wrote: >>I can get the first sleep. Suppose I oversleep by X nanoseconds. I >>wake, and get an opaque timeout back. How do I ask for the new wake >>time to be "endtime + INTERVAL"? > > > endtime.ts += INTERVAL > [we all know opaque is relative too] Heh. Okay, then what are the rules about what I'm allowed to do with endtime? Joe mentioned there was a bit in there somewhere to denote absolute time. > Or better, use itimers :) I as actually thinking in terms of implementing itimers on top of your new API. Chris