Date: Mon, 1 Nov 1999 13:19:19 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: "Justin T. Gibbs" <gibbs@freebsd.org> Cc: Nate Williams <nate@mt.sri.com>, Peter Dufault <dufault@hda.com>, freebsd-arch@freebsd.org Subject: Re: Threads models and FreeBSD. Message-ID: <Pine.BSF.4.10.9911011317510.1462-100000@current1.whistle.com> In-Reply-To: <199911011914.MAA00659@caspian.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
there is no guarantee that thread specific storage is 'private' only that when you access it from each thread you end up pointing to a different place (physically). the use of an index register or some other trick satisfies this requirement. On Mon, 1 Nov 1999, Justin T. Gibbs wrote: > >> > Thread share everything that a normal process, including a > >> > thread-specific stack which is used to keep each thread's context > >> > seperate from one another. > >> > >> I haven't caught up with you guys yet. This is what > >> I asked about POSIX threading before: can stack be private per > >> thread? > > > >I don't believe so, although each thread does have it's own stack, it's > >not private. Sean would know more though.... > > What about thread local storage? > > -- > Justin > > > 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?Pine.BSF.4.10.9911011317510.1462-100000>