From owner-freebsd-smp Wed May 1 13:22:55 2002 Delivered-To: freebsd-smp@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0BC3737B416; Wed, 1 May 2002 13:22:46 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA16405; Wed, 1 May 2002 16:22:45 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g41KMFU26818; Wed, 1 May 2002 16:22:15 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15568.20086.979721.992191@grasshopper.cs.duke.edu> Date: Wed, 1 May 2002 16:22:14 -0400 (EDT) To: John Baldwin Cc: freebsd-smp@FreeBSD.org Subject: RE: hlt when idle? In-Reply-To: References: <15567.62317.677224.3470@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin writes: > > On 01-May-2002 Andrew Gallatin wrote: > > > > > > Can somebody remind me why we do not hlt in the idle loop on MP x86s? > > Is this because a HLTed CPU is not going to notice a new runnable job > > (possibly migrating from another CPU) until it gets an interrupt to > > wake it up? > > Yes. This seems to be an acceptable "loss" in performance in environments where cooling is a concern. Is there a deadlock danger? Or is it just a performance tweak to not HLT SMPs? Would you object to making it a sysctl (machdep.smp_idle_hlt)? > > Do both CPUs get clock interrupts on x86? > > No, the interrupts seem to be round-robin, but each clock intr is only > sent to one CPU unlike on alpha where they are broadcast. So each CPU gets (1/num_cpu) * hz clock interrupts/sec? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message