Date: Thu, 13 Nov 2003 02:06:27 -0800 From: "Eugene M. Kim" <ab@astralblue.net> To: freebsd-hackers@freebsd.org Subject: cpu_idle_hlt (Re: Confused about HyperThreading and Performance) Message-ID: <3FB357A3.4030907@astralblue.net> In-Reply-To: <XFMail.20031112180758.jhb@FreeBSD.org> References: <XFMail.20031112180758.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > Also, as someone else mentioned, setting 'machdep.cpu_idle_hlt=1' can > be useful on some HTT systems. However, p4's have a problem with their > interrupt routing that can leave the second CPU halted for a long time > if you do that. I have a few quick questions... Searched on Google but couldn't get satisfactory answers: 1. Without cpu_idle_hlt, is the problem that the idle spin loop one logical CPU executes would eat up CPU time and prevent the other logical CPU from running? 2. If so, would it explain the unusually high percentage of system time and unusually low percentage of user time (shown on systat -vm 1) when processes should be mostly doing CPU work and some heavy disk I/O at the same time? 3. Is cpu_idle_hlt also potentially unsafe on P4 Xeon-based SMP systems? Thanks, Eugene P.S. It'd be greatly appreciated if someone could point to an in-depth discussion about Hyperthreading and cpu_idle_hlt... *yells at his poor Googling skill XD*
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FB357A3.4030907>