Date: Tue, 07 Sep 2010 20:15:17 +0530 From: "Cherry G. Mathew" <cherry@zyx.in> To: Alexander Motin <mav@FreeBSD.org>, freebsd-arch@freebsd.org Subject: [resend] Re: RFC: New event timers infrastructure Message-ID: <4C864FFD.6020409@zyx.in> In-Reply-To: <4C0C1AE4.8050807@FreeBSD.org> References: <4C0C1AE4.8050807@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear Alexander, On 6/6/2010 10:02 PM, Alexander Motin wrote: > > I did such things: > - created unified timer driver's API (sys/timeet.h, kernel/kern_et.c). > It supports global and per-CPU timers, periodic and one-shot. Provides > driver and consumer interfaces for choosing timers and operating them; [...] > Latest patches can be found here: > http://people.freebsd.org/~mav/et.20100606.patch > [...] > > Feedback is very appreciated. > Had you considered integrating this api with sys/timetc.h ? Most timer devices which can interrupt after a certain period of time, can also provide counters, I would imagine ? I'd be keen to know your thoughts on providing the ability of et consumers to daisy chain to a single eventtimer. It would be good for et_find() to query for timers that can guarantee a specific resolution/period or below/above. Finally, I'm curious to know what et_quality implies ? Perhaps it can be an indication of the max/min resolution/period available from a given et ? Many Thanks, -- cherry PS: please Cc: me too - I'm not on-list.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C864FFD.6020409>