Date: Wed, 22 Nov 2000 14:13:23 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Alfred Perlstein <bright@wintelcom.net> Cc: arch@FreeBSD.org, Arun Sharma <arun@sharmas.dhs.org>, Daniel Eischen <eischen@vigrid.com> Subject: Re: Thread-specific data and KSEs Message-ID: <XFMail.001122141323.jhb@FreeBSD.org> In-Reply-To: <20001122133421.S18037@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22-Nov-00 Alfred Perlstein wrote: > * John Baldwin <jhb@FreeBSD.ORG> [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 <jhb@FreeBSD.org> -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.001122141323.jhb>