From owner-freebsd-hackers Wed Jan 6 05:21:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15768 for freebsd-hackers-outgoing; Wed, 6 Jan 1999 05:21:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15763 for ; Wed, 6 Jan 1999 05:21:46 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id NAA21632; Wed, 6 Jan 1999 13:21:18 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma021627; Wed, 6 Jan 99 13:21:07 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zxstX-00060r-00; Wed, 6 Jan 1999 13:21:07 +0000 To: hackers@FreeBSD.ORG From: Tony Finch Subject: Re: pthreads question/problem... In-Reply-To: References: <369296F4.AE24010B@canonware.com> Message-Id: Date: Wed, 6 Jan 1999 13:21:07 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > >In fact we have a port of the linux threads to FreeBSD so we can do >EXACTLY what they do, including the kernel support. It's being worked on >as we speak. Some is already committed to -current. There is little >argumant however that the ultimate is to schedule N threads over M >processes where M is related to teh number of CPUs available. Sometimes you want M to be large relative to the number of CPUs because you are using threading to improve userland IO concurrency. Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message