From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <290c102a9496a5f2a33af7922d24382e@yourdomain.dom> To: 9fans@cse.psu.edu Cc: torvalds@osdl.org 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 01:31:41 -0500 Topicbox-Message-UUID: fd59fc7c-eacc-11e9-9e20-41e7f4b1d025 > (1) There are valid reasons to pass pointers between threads, and yes, > they can be pointers to thread stack areas. Do you have code from existing Linux implementation that exemplifies this scenario? What are your opinions on the benefits? If there is existing code that exemplifies this scenario, how often does it propagate? Is it often enough to denounce a standard interface in the kernel? Also, what are your comments, Linus, on shared library execution altering the scope of an interface from kernel context to user context? Even if there isn't a unified stack, there is still an interface defined by such thread projects as POSIX threads, etc. Doesn't that just create a standard interface in user- land that could be sped up, if moved to kernel context? Don (north_)