Hi,

I like that quick shot. Although of course this would only take effect for 
timers which are not already running. But I think anyway it is unsane to change 
timers which are already running.


Best regards,

Daniel Schnell.



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 3. maĆ­ 2007 18:47
To: Gilles Chanteperdrix
Cc: Daniel Schnell; [email protected]
Subject: Re: [Xenomai-help] Latency calculation and test

Gilles Chanteperdrix wrote:
> Daniel Schnell wrote:
>  >
>  > If, say, I would use latencies calibrated with user space POSIX  > 
> timers for a typical work load, what would happen to timers that are  
> > running in kernel or interrupt space ? Would they then be too early ?
>  > Have negative values any negative effect besides running too early ?
>  >
>  > In other words: when one uses timers inside Kernel, ISR's and User  
> > space at the same time, which value should be used for  > 
> /proc/xenomai/latency ? Wouldn't it make sense then to have 3  > 
> different latency values for the 3 possible environments ?
> 
> Yes the current situation is that there is only one constant, so, if 
> you calibrate it for ISRs, user-space programs will be systematically 
> late. Having three different constants would mean that we track, at 
> nucleus level where each timer is used, and that we order timers in 
> the timer queue according to their anticipated expiration date. This 
> is quite a modification.

Quick shot: Maybe the caller of xntimer_start could already account for the 
usage scenario and subtract some magic offset from the timeout date.

Jan


_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to