From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: [9fans] Re: Threads: Sewing badges of honor onto a Kernel
From: Dave Lukes <davel@anvil.com>
To: Linus Torvalds <torvalds@osdl.org>, 9fans <9fans@cse.psu.edu>
In-Reply-To: <Pine.LNX.4.58.0402262247470.2563@ppc970.osdl.org>
References: <290c102a9496a5f2a33af7922d24382e@yourdomain.dom>
	 <Pine.LNX.4.58.0402262247470.2563@ppc970.osdl.org>
Content-Type: text/plain
Message-Id: <1077884597.21772.21.camel@zevon>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Date: Fri, 27 Feb 2004 12:23:17 +0000
Topicbox-Message-UUID: ffb95eae-eacc-11e9-9e20-41e7f4b1d025

> > Do you have code from existing Linux implementation that exemplifies
> > this scenario?

... and I'm _still_ waiting for an answer.

> Anything that accesses any process arguments would access the stack of the
> original thread.

... which is copied, so what's the problem?
Do you want all the threads to be able to _update_ the process args?
That's harder, and also more dubious.

>  But synchronization with
> completion events on the stack is also perfectly feasible (the kernel does
> exactly that internally, for example - and user mode could do the same).

The kernel using it is an implementation detail.
User mode using it: show me the example!

Cheers,
	Dave.