Message-ID: <428CC6B5.3070206@mvista.com>
Date: Thu, 19 May 2005 10:02:45 -0700
From: George Anzinger <george@mvista.com>
Reply-To: george@mvista.com
Organization: MontaVista Software
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Fedora/1.7.6-1.3.2
MIME-Version: 1.0
To: Andi Kleen <ak@muc.de>
CC: joe.korty@ccur.com, robustmutexes@lists.osdl.org,
       linux-kernel@vger.kernel.org
Subject: Re: [RFC] A more general timeout specification
References: <20050518201517.GA16193@tsunami.ccur.com> <m1hdh0yu14.fsf@muc.de>
In-Reply-To: <m1hdh0yu14.fsf@muc.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1267
Lines: 30

Andi Kleen wrote:
~>
> 
> 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. This helps
> optimizing the idle loop because you can batch timers better and is
> important for power management and virtualized environments. The
> kernel internally does not use support this yet, but there are plans
> to change the internal timers in this direction and if you're defining
> a new user interface I would add support for this.
> 
> I am not sure precision would be the right name, other suggestions
> are welcome.
>

I think the accepted and standard way to do this is to use different "clock"s. 
For example, in the HRT patch the clocks CLOCK_REALTIME_HR and 
CLOCK_MONOTONIC_HR are defined as high resolution clocks.
> 
~
-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
-
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/