Date: Tue, 21 Nov 2000 16:07:50 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: arch@FreeBSD.org, Daniel Eischen <eischen@vigrid.com> Subject: Re: Thread-specific data and KSEs Message-ID: <XFMail.001121160750.jhb@FreeBSD.org> In-Reply-To: <20001121175655.T19895@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21-Nov-00 Jonathan Lemon wrote: > On Tue, Nov 21, 2000 at 06:51:59PM -0500, Daniel Eischen wrote: >> I'm going to start working on the user-side of the new threads >> library. I need to be able to quickly get at the current KSE >> (or perhaps KSEG). Can we define a register on each architecture >> that should not be used by FreeBSD ABI compliant applications? >> The register doesn't have to be 32 bits or larger, just large >> enough to hold the maximum number of KSEs (or KSEGs). > > Um. On a i386 I'm not sure this will be practical, there aren't > a whole lot of architecturally visible registers for use by the > application. Agreed. Just use a regulare per-CPU data variable the same way that 'curproc' is implemented right now. > -- > Jonathan -- 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.001121160750.jhb>