On Tue, 2006-07-25 at 20:26 +0200, Jan Kiszka wrote:
massive snippage
To summarise these lengthy results:
o ns-based xntimers are nice on first sight, but not on second. Most
use-cases (except 5) require less conversions when we keep the
abstraction as it is.
The current
On Thu, 2006-07-27 at 14:42 +0200, Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
o A further improvement should be achievable for scenarios 4 and 5 by
introducing absolute xntimers (more precisely: a flag to
differentiate between the mode on xntimer_start). I have an
On Thu, 2006-07-27 at 15:54 +0200, Jan Kiszka wrote:
Philippe Gerum wrote:
On Thu, 2006-07-27 at 14:42 +0200, Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
o A further improvement should be achievable for scenarios 4 and 5 by
introducing absolute xntimers (more precisely: a
Hi all,
to continue the discussion about improving the timer subsystem,
specifically with respect to unit conversion overhead, I'm posting here
a (fairly long) report of my findings and consideration.
First of all I did some benchmarking of the various optimised conversion
routines that popped
Hi,
while I originally only wanted to add timer abstraction to RTDM, I now
have patch series for xntimer pending on my box pushing this layer
closer to hrtimer.
But before posting it for discussion (needs further testing anyway), I
have two questions regarding some minor though not totally
