From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] Re: Threads: Sewing badges of honor onto a Kernel From: C H Forsyth In-Reply-To: <20040227122445.H22848@cackle.proxima.alt.za> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-zqwyotoqzrvbnjjxngsbgwkwpa" Date: Fri, 27 Feb 2004 11:40:20 +0000 Topicbox-Message-UUID: ffe28b3a-eacc-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-zqwyotoqzrvbnjjxngsbgwkwpa Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit sorry, when i said `private' i meant `for that process's exclusive use as a stack', not that it was in a per-process address space. it's per-process only in that by agreement the process to which it is given is the only one that uses it as a stack (the others can still access its contents if they like, but often they don't). they are all still in the same address space. they could be allocated (essentially) by malloc, except that you need to ensure they are all aligned appropriately (eg, at an address that is 0 mod KSTACK in that previous example). --upas-zqwyotoqzrvbnjjxngsbgwkwpa Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by doppio; Fri Feb 27 10:30:25 GMT 2004 Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id BADBD19D97; Fri, 27 Feb 2004 05:25:23 -0500 (EST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 9940D19E06; Fri, 27 Feb 2004 05:25:19 -0500 (EST) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id E324A19DD5; Fri, 27 Feb 2004 05:24:49 -0500 (EST) Received: from cackle.proxima.alt.za (cackle.proxima.alt.za [196.30.44.141]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id CF7A819D6F for <9fans@cse.psu.edu>; Fri, 27 Feb 2004 05:24:47 -0500 (EST) Received: from cackle.proxima.alt.za (localhost [127.0.0.1]) by cackle.proxima.alt.za (8.12.8/8.12.3) with ESMTP id i1RAOl0V014573 for <9fans@cse.psu.edu>; Fri, 27 Feb 2004 12:24:48 +0200 (SAST) Received: (from lucio@localhost) by cackle.proxima.alt.za (8.12.8/8.12.3/Submit) id i1RAOkee014572 for 9fans@cse.psu.edu; Fri, 27 Feb 2004 12:24:46 +0200 (SAST) From: Lucio De Re To: 9fans@cse.psu.edu Subject: Re: [9fans] Re: Threads: Sewing badges of honor onto a Kernel Message-ID: <20040227122445.H22848@cackle.proxima.alt.za> Mail-Followup-To: 9fans@cse.psu.edu References: <20040227120737.G22848@cackle.proxima.alt.za> <546b0d5927ae22ab3a714cabaaa0f47a@terzarima.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <546b0d5927ae22ab3a714cabaaa0f47a@terzarima.net>; from Charles Forsyth on Fri, Feb 27, 2004 at 10:14:32AM +0000 Organization: Proxima Research & Development Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu X-Reply-To: lucio@proxima.alt.za List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Fri, 27 Feb 2004 12:24:46 +0200 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psuvax1.cse.psu.edu X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Level: On Fri, Feb 27, 2004 at 10:14:32AM +0000, Charles Forsyth wrote: > > >>Yeow! And where do I put the returned address, so that no other thread > >>can stomp on it? While I attempt to use it? > > the process is running by then on its own stack, so the result is either in > a register (EAX say) or in a temporary on the stack but either way, it's private. > Sure, but I thought the idea was that all storage was shared, except any that was privately allocated later. Did I read wrong Torvalds' comments about the stack being nothing special? And then a new private stack comes along? How is it initialised? Isn't it a duplicate? I think I'm out of my depth. ++L --upas-zqwyotoqzrvbnjjxngsbgwkwpa--