From owner-freebsd-questions Thu Jan 20 9:38:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from skygod.cns.ksu.edu (skygod.cns.ksu.edu [129.130.61.25]) by hub.freebsd.org (Postfix) with ESMTP id 0BF5614C37 for ; Thu, 20 Jan 2000 09:38:43 -0800 (PST) (envelope-from beemern@ksu.edu) Received: from ksu.edu ([129.130.61.24]) by skygod.cns.ksu.edu (8.9.2/8.9.2) with ESMTP id MAA19918 for ; Thu, 20 Jan 2000 12:10:43 -0600 (CST) (envelope-from beemern@ksu.edu) Message-ID: <38874884.B6CA4A21@ksu.edu> Date: Thu, 20 Jan 2000 11:40:20 -0600 From: nathan X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: kernel threads Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hmmm i've been playing a bit with threads. I'm running 3.3-RELEASE + SMP (dual pIII/450's) anyway... i didn't mess with installing the linux_threads port i noticed that there already is a pthread.h header file on my system i was looking at the Parallel Processing HOWTO from the LDP (linux documentation project) i compiled and ran their sample code for computing Pi (the linear version) and THEN i dl'd /compiled/ ran the pthread version of computing Pi by doing a gcc -pthread file.c it compiled right away and ran fine. comparing "time" between the two binaries, i got a 16% increase in speed using the pthread version versus the linear version. my question... what does all this mean as it relates to this thread? (no pun intended) i ran across something somewhere where the linux_threads port was outdated, or already included in the 3.x versions.. just curious as to what all this means, as the code source was from a Linux HOWTO. thanks! Scott Hess wrote: > As far as I can tell it doesn't even _compile_ under 3.x, much less run, > with or without SMP. > > Later, > scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message