From owner-freebsd-questions Sun Nov 14 15:29:28 1999 Delivered-To: freebsd-questions@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 6361714C41; Sun, 14 Nov 1999 15:29:22 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with smtp (Exim 1.92 #3) id 11n95G-000CDE-00; Sun, 14 Nov 1999 23:29:22 +0000 Date: Sun, 14 Nov 1999 23:29:21 +0000 (GMT) From: Jonathon McKitrick To: Kris Kennaway Cc: freebsd-questions@freebsd.org Subject: Re: threads.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Nov 1999, Kris Kennaway wrote: >On Sun, 14 Nov 1999, Jonathon McKitrick wrote: > >> I've seen 'FUD' a lot, and I know it's not good... what does it mean >> again? > >Read the jargon file. > >> Also, from what I understand, the issue with threads is in the kernel, >> not user space. If I understand correctly, the kernel is not threaded, >> which means that all processes must wait one at a time for each kernel >> call to finish, since it cannot be pre-empted. It this correct? I saw >> an earlier post saying that Linux has a jump on this. > >This is an unrelated issue (Linux isn't very much beyond FreeBSD here). > >> I understand that user threads are supported, but apparently the issue >> is kernel threads. > >You still haven't explained how. OK, then, let me ask this: Just what _is_ the thread support Linux has that FreeBSD doesn't have at the moment? I will procede once I have an accurate answer to this question. Apparently FreeBSD still multitasks quite well without this feature, but that doesn't mean it shouldn't be a future design goal. > >Kris > >---- >Cthulhu for President! For when you're tired of choosing the _lesser_ of >two evils.. > > -jonathon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message