From owner-freebsd-arch Wed Nov 22 15: 7:50 2000 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 00E2937B479; Wed, 22 Nov 2000 15:07:49 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA08419; Wed, 22 Nov 2000 18:07:27 -0500 (EST) Date: Wed, 22 Nov 2000 18:07:27 -0500 (EST) From: Daniel Eischen To: Alfred Perlstein Cc: John Baldwin , Arun Sharma , arch@FreeBSD.ORG Subject: Re: Thread-specific data and KSEs In-Reply-To: <20001122133421.S18037@fw.wintelcom.net> 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 Wed, 22 Nov 2000, Alfred Perlstein wrote: > * John Baldwin [001122 13:06] wrote: > > > > Eh, I would use a small LDT (LDT's don't have to be large if you don't have a > > lot of selectors) for each KSE with one statically configured selector that %gs > > is always set to that will point to the KSE data. Thus, when you create a KSE, > > you just setup its LDT to have the KSE data entry point to the KSE data. > > Was there something wrong with the suggestion to put the local info > on the stack? I just don't see it being discussed at all. Yes, I stated that it could not be used. We want to provide a POSIX complaint API, and this dictates that applications be able to create stacks of their own size and choosing. We can't rely on stacks being any particular size, or starting at any particular address. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message