From owner-freebsd-questions Fri Mar 16 20:20:18 2001 Delivered-To: freebsd-questions@freebsd.org Received: from suntan.cyberbeach.net (suntan.cyberbeach.net [216.223.72.20]) by hub.freebsd.org (Postfix) with ESMTP id B1F2837B718 for ; Fri, 16 Mar 2001 20:20:15 -0800 (PST) (envelope-from gldis@cyberbeach.net) Received: from papasmurf (ppp103-25.sudbury.cyberbeach.net [216.104.103.25]) by suntan.cyberbeach.net (8.9.1/8.9.1) with SMTP id XAA19835; Fri, 16 Mar 2001 23:20:22 -0500 (EST) Message-ID: <019501c0ae9a$4c6ecba0$0201a8c0@my.domain> From: "e" To: "Mike Meyer" , "Dorr H. Clark" Cc: References: <15025.36392.539952.340643@guru.mired.org> Subject: Re: MP & FreeBSD Date: Fri, 16 Mar 2001 23:25:27 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm sure there are people who could be considered to be leading the > development, but I'm not sure who they are. At this point, pretty much > everyone working on the kernel has to deal with SMP. I'd say it's > already a mainstream capability. It's just not enabled by default. I > expect it's of low enough utility that it's deemed not worth the > cost. Then again, it might just cause horrible things to happen on > some older (386 or 486) UP boards. http://people.freebsd.org/~jasone/smp/ An SMP kernel won't boot on a UP system. So the lack users with SMP hardware would be the reason for not enabling the SMP code in the GENERIC kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message