From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: torvalds@osdl.org Cc: 9fans@cse.psu.edu Subject: Re: [9fans] Re: Threads: Sewing badges of honor onto a Kernel From: dbailey27@ameritech.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Fri, 27 Feb 2004 02:46:19 -0500 Topicbox-Message-UUID: fdadd0e0-eacc-11e9-9e20-41e7f4b1d025 > The rationale is that it's incredibly more sane, and it's the logical > place to put something that (a) needs to be allocated thread-specific and > (b) doesn't need any special allocator. You've just proven my point. Thread specific. Being Thread specific, it is data that is reserved to the scope of a single thread. Nothing more. If you want more scope there are many more usages of memory that are better utilized. I'm not arguing against automatic variables. I'm arguing against using automatic variables anywhere but the scope of stack in which they are defined. I don't know where you're getting religiousness, but, there's nothing wrong with trying to do the best for all of your users. That's why companies research their target audience, so they can improve a product according to the most global needs of a given group. Don (north_)