From owner-freebsd-stable Sun Dec 10 0:26:11 2000 From owner-freebsd-stable@FreeBSD.ORG Sun Dec 10 00:26:09 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (unknown [209.10.218.74]) by hub.freebsd.org (Postfix) with ESMTP id 82C6437B400 for ; Sun, 10 Dec 2000 00:26:07 -0800 (PST) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Sun, 10 Dec 2000 00:25:01 -0800 From: "David Schwartz" To: "Noor Dawod" Cc: Subject: RE: MySQLd not using both CPUs Date: Sun, 10 Dec 2000 00:26:06 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-reply-to: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why should I use LinuxThreads to make use of more than one CPU? I mean, > how come that FreeBSD's threads library doesn't support this, and will > it ever? (maybe it's in development even now...) > > Noor The FreeBSD port of LinuxThreads _is_ a FreeBSD thread library. It's not emulation or anything, it's a threads library for FreeBSD native code. The pthreads implementation included with FreeBSD (libc_r) is really just not useful for high-performance or high-reliability applications. In my experience, it works very well for bad code and very badly for good code. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message