Date: Mon, 5 Jul 2004 08:04:34 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Daniel Eischen <eischen@vigrid.com> Cc: freebsd-threads@freebsd.org Subject: Re: pthread switch (was Odd KSE panic) Message-ID: <Pine.BSF.4.21.0407050801530.66234-100000@InterJet.elischer.org> In-Reply-To: <Pine.BSF.4.21.0407050704310.66234-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Jul 2004, Julian Elischer wrote: > > > > I suspect that as clock ticks occur at only 10mSEC period, that it will > nearly always be the 2nd option. In other words the system is acting as > it would with a uniprocessor. > > compare this with: > add up: > > time to for 'waker' to enter the UTS > time for the UTS to decide it can awaken another KSE > time for the UTS to call kse_wakeup() (from kerne entry to "wakeup()") > time for UTS to return to original thread > time for UTS to switch to other thread. > (*) this is what is being measured here.. > > however the 'select' thread wil be restarted when the other thread > completes and re-does the wait OR a clock tick occurs. > > Drew, what happens to the 47uSec if you do: sysctl machdep.cpu_idle_hlt=0 ? > > julian > > > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0407050801530.66234-100000>