From owner-freebsd-arch Wed Nov 22 14:13:28 2000 Delivered-To: freebsd-arch@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 1E08437B4F9 for ; Wed, 22 Nov 2000 14:13:25 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAMMDB059168; Wed, 22 Nov 2000 14:13:11 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001122133421.S18037@fw.wintelcom.net> Date: Wed, 22 Nov 2000 14:13:23 -0800 (PST) From: John Baldwin To: Alfred Perlstein Subject: Re: Thread-specific data and KSEs Cc: arch@FreeBSD.org, Arun Sharma , Daniel Eischen Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Nov-00 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. No, I was just exploring the possibility of the original request of using a register to do it. Using the stack may not be bad idea, although using a register would be more consistent with how we treat per-CPU data in the kernel. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message