From owner-freebsd-smp Wed Aug 18 11:21:38 1999 Delivered-To: freebsd-smp@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id A3CA5151BA for ; Wed, 18 Aug 1999 11:21:15 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2448.0) id ; Wed, 18 Aug 1999 12:21:04 -0600 Message-ID: <64003B21ECCAD11185C500805F31EC0303786DA1@houston.matchlogic.com> From: Charles Randall To: freebsd-smp@FreeBSD.ORG Subject: SMP differences between -stable and -current (RE: wine and SMP) Date: Wed, 18 Aug 1999 12:21:04 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Note: only to -smp] Which of those limitations also apply to -current? Charles -----Original Message----- From: Bruce Albrecht [mailto:bruce@zuhause.mn.org] ... Even though SMP is supported in -stable, you must recognize that it's a fairly weak implementation. For the most part, there's only one kernel lock, so in general, you can't have more than one CPU doing kernel stuff, even though the two kernel requests (for example, two separate disk controllers, or two NICs) are independent of each other. There's no processor affinity. A threaded process can't have multiple threads running simultaneously on multiple CPUs. I'm sure there are other deficiencies I've left out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message