From owner-freebsd-arch Wed Nov 22 13:34:49 2000 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9BD9937B479; Wed, 22 Nov 2000 13:34:47 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAMLYLb23588; Wed, 22 Nov 2000 13:34:21 -0800 (PST) Date: Wed, 22 Nov 2000 13:34:21 -0800 From: Alfred Perlstein To: John Baldwin Cc: Daniel Eischen , Arun Sharma , arch@FreeBSD.ORG Subject: Re: Thread-specific data and KSEs Message-ID: <20001122133421.S18037@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Wed, Nov 22, 2000 at 01:06:04PM -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * 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. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message