Messages in this thread |  | | Date | Mon, 20 Jan 2003 22:52:11 -0800 | From | george anzinger <> | Subject | [PATCH NOTICE] POSIX clocks & timers take 21 (NOT HIGH RES) |
| |
The 2.5.59 version of this patch is now available on sourceforge (see signature).
Changes since last time:
--------------- Fixed a spin lock hand off problem in locking timers (thanks to Randy). Fixed nanosleep to test for out of bound nanoseconds (thanks to Julie). Fixed a couple of id deallocation bugs that left old ids laying around (hay I get this one). ----------- This version has a new timer id manager. Andrew Morton suggested elimination of recursion (done) and I added code to allow it to release unused nodes. The prior version only released the leaf nodes. (The id manager uses radix tree type nodes.) Also added is a reuse count so ids will not repeat for at least 256 alloc/ free cycles. -----------
The changes for the new sys_call restart now allow one restart function to handle both nanosleep and clock_nanosleep. Saves a bit of code, nice.
All the requested changes and Lindent too :).
I also broke clock_nanosleep() apart much the same way nanosleep() was with the 2.5.50-bk5 changes.
This is still this way. Should be easy to do the compat stuff.
TIMER STORMS
The POSIX clocks and timers code prevents "timer storms" by not putting repeating timers back in the timer list until the signal is delivered for the prior expiry. Timer events missed by this delay are accounted for in the timer overrun count. The net result is MUCH lower system overhead while presenting the same info to the user as would be the case if an interrupt and timer processing were required for each increment in the overrun count. -- George Anzinger george@mvista.com High-res-timers: http://sourceforge.net/projects/high-res-timers/ Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml - 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/
|  |