From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucio De Re To: 9fans@cse.psu.edu Cc: dbailey27@ameritech.net, Linus Torvalds Subject: Re: [9fans] Re: Threads: Sewing badges of honor onto a Kernel Message-ID: <20040227103130.E22848@cackle.proxima.alt.za> References: <20040227101110.E24932@cackle.proxima.alt.za> <64FBCAEA-68FD-11D8-B851-000A95B984D8@mightycheese.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <64FBCAEA-68FD-11D8-B851-000A95B984D8@mightycheese.com>; from Rob Pike on Fri, Feb 27, 2004 at 12:17:33AM -0800 Date: Fri, 27 Feb 2004 10:31:30 +0200 Topicbox-Message-UUID: fe01202e-eacc-11e9-9e20-41e7f4b1d025 On Fri, Feb 27, 2004 at 12:17:33AM -0800, Rob Pike wrote: > > On Feb 27, 2004, at 12:11 AM, Lucio De Re wrote: > > > Of course, I may be talking out of turn, but I really don't see > > how threads can have private space if the stack isn't private. > > well, perhaps the stack isn't the only place to do it, but it's > certainly an easy one, and one that makes the syscall interface > to fork easy to implement in a threaded environment: longjmp > to the private stack, fork, adjust, longjmp back. > But I can't think of even one possible alternative. After all, the stack is the only storage being duplicated (ignoring registers) so where does one keep pointers to the private space? ++L