From owner-freebsd-arch Sun Oct 31 18:17:28 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 5ED6614BD7 for ; Sun, 31 Oct 1999 18:17:18 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id DAA00987 for ; Mon, 1 Nov 1999 03:17:17 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA69255 for freebsd-arch@freebsd.org; Mon, 1 Nov 1999 03:17:16 +0100 (MET) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1975614BD7 for ; Sun, 31 Oct 1999 18:16:49 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id SAA30144; Sun, 31 Oct 1999 18:16:45 -0800 (PST) Date: Sun, 31 Oct 1999 18:16:43 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: Nate Williams Cc: freebsd-arch@freebsd.org Subject: Re: Threads models and FreeBSD. In-Reply-To: <199911010158.SAA13775@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 Oct 1999, Nate Williams wrote: > > > > maybe I should reword it to: > > > > "Inability of one thread to unwittingly block another thread during normal > > > > operations" ? > > > > > > How about the abilty for multiple threads to execute at the same time? > > > :) > > well that requires multiple processors.. > > > > see #2 > > maybe I need to make it more explicit? > > > > It's the 'inability to block' that gets me. see new improved wording to follow > > > > > > > 4/ All threads see the same address space (exactly). > > > > > > > > > > > > 5/ All threads share the same file resources. > > > > > > > > > > All threads share all the same resources (except for thread-specific stack). > > > > Well they can see all the other stacks, they just don't use them as the > > > > stack. How would you better word that? > > > > > > The resources are *all* shared (not just file resources), but each > > > thread has it's own thread-specific stack. > > > > ok gimme a better wording.. yours leads me to wonder if there is > > somethign special about the mamory a particular thread's stack is on.. > > That's the only thing that is not 'shared' across threads. Everything > else is shared. but that's wrong.. the memory is shared.. only the %sp register is differnet.. > > > (they don't share processor registers BTW, nor do they neccesarily share > > proccessors if they have affinity) > > That's an implementation issue. I think most clued folks will > understand that registers aren't shared, although in some cases they > might be. :) > > > > Nate > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message