Messages in this thread | | | Subject | Re: Robust futexes | From | Rusty Russell <> | Date | Sat, 18 Feb 2006 14:53:32 +1100 |
| |
On Fri, 2006-02-17 at 10:13 +0100, Ingo Molnar wrote: > * Paul Jackson <pj@sgi.com> wrote: > > > So the point is that we only have to cleanup the stale locks of dead > > threads when some other task has the misfortune of trying to take the > > orphaned lock and gets forced into a wait. > > > > The wait call essentially becomes a "wait unless said other TID is > > dead, in which case, a new owner is summarily declared." > > the fundamental problem i see here: how do you 'declare' a TID as dead? > 32-bit TIDs can be reused, quite fundamentally.
Yes. I was asking of we actually need prefect robustness. I'm fairly confident that this approach would work well in practice, since if tids are being churned, the thread with wrapped TID will exit soon anyway.
I mentioned the possibility to make sure you had considered it.
As an added bonus, the tone of the first response I received (not yours!) reminded me why I am not subscribed to lkml...
Cheers! Rusty. -- ccontrol: http://ozlabs.org/~rusty/ccontrol
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |