Date: Fri, 28 Oct 2005 14:43:53 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: David Xu <davidxu@freebsd.org> Cc: Pertti Kosunen <pertti.kosunen@pp.nic.fi>, Poul-Henning Kamp <phk@phk.freebsd.dk>, current@freebsd.org, "Yuriy N. Shkandybin" <jura@networks.ru> Subject: Re: Timers and timing, was: MySQL Performance 6.0rc1 Message-ID: <20051028144307.X53858@fledge.watson.org> In-Reply-To: <436229CF.6040001@freebsd.org> References: <32412.1130505646@critter.freebsd.dk> <436229CF.6040001@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Oct 2005, David Xu wrote: > Poul-Henning Kamp wrote: > >>> On the other hand, a lower risk change might be to simply add a new >>> CLOCK_ type for lower resolution, and have a timer synchronize a >>> variable to the system clock once every 1/10 of a second. This avoids >>> having to muck with VM layout, etc. >> >> Is the CLOCK_* namespace ours to muck about with in the first place ? >> > I prefer this way, can you implement it? The global page idea is a > complex, someone can slowly work on it, there are many things can be > done, for example, fast syscall using sysenter/sysexit. I'm happy to take a stab at this. We still need someone to grab the context switch time keeping by the horns and Do Something, though. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051028144307.X53858>