Date: Thu, 19 Sep 1996 10:31:23 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Terry Lambert <terry@lambert.org> Cc: dg@Root.COM, bde@zeta.org.au, proff@suburbia.net, freebsd-hackers@FreeBSD.org Subject: thread stacks and protections (was Re: attribute/inode caching) Message-ID: <Pine.SV4.3.93.960919101646.12359A-100000@parkplace.cet.co.jp> In-Reply-To: <199609171816.LAA04481@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 17 Sep 1996, Terry Lambert wrote: > Personally, I'd like to use page anonymity based protections to establish > Chorus-like access priveledge domains for IPC; specifically, for stacks > capable of being grown by fault for use by threads. I think the POSIX > model is broken: I should not be required to preallocate stack for a > thread just because SVR4 and Solaris have bogus architectures (actually, > the SVR4 VM does *not* impose this limitation: it is a limitation of > the threading code alone. Steve Baumel, the author of the SVR4 VM, and > I discussed this at some length when discussing context sharing models > that would be useful for the NetWare for UNIX product). > How does one implement a u-area concept on top of Chorus? A lot of stuff that used to be in the u-area has been moved out to the proc and other structures in 4.4BSD. Maybe moving the kernel stack out of the u-area and generalizing the proc and u-cred stuff can be a step toward what your talking about. Regards, Mike Hancock
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.93.960919101646.12359A-100000>