From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucio De Re To: Linus Torvalds Cc: 9fans@cse.psu.edu Subject: Re: [9fans] Re: Threads: Sewing badges of honor onto a Kernel Message-ID: <20040227121350.K24932@cackle.proxima.alt.za> References: <20040227101110.E24932@cackle.proxima.alt.za> <64FBCAEA-68FD-11D8-B851-000A95B984D8@mightycheese.com> <20040227103130.E22848@cackle.proxima.alt.za> <20040227115257.F22848@cackle.proxima.alt.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Linus Torvalds on Fri, Feb 27, 2004 at 02:11:27AM -0800 Date: Fri, 27 Feb 2004 12:13:51 +0200 Topicbox-Message-UUID: ff3252e2-eacc-11e9-9e20-41e7f4b1d025 On Fri, Feb 27, 2004 at 02:11:27AM -0800, Linus Torvalds wrote: > > On Fri, 27 Feb 2004, Lucio De Re wrote: > > > On Fri, Feb 27, 2004 at 01:46:27AM -0800, Linus Torvalds wrote: > > > > > > Why are you ignoring registers? That's what you _should_ use. > > > > Because they are not in the base language? Because they impair > > portability? > > You literally need _one_ operation: you need the operation of "give me the > TLS pointer" (well, your thread setup code obviously needs a way to set > the pointer when creating a thread too). > Yes, but... > > Because in my C code, I can't instantiate them as variables without > > running the risk of my colleagues doing the same in a conflicting > > manner? > > Unless I'm missing the wood for the trees, this returns a pointer. Where do I put _it_ so no other thread, choosing to do likewise, decides to stomp all over it? ++L