Hmm.. The workarounds make me suspect that maybe your right interface was
the right one after all.
This interface has the advantage that the exit() path for this kind of
child has _zero_ context switching overhead etc, so I do like it. Although
I get this feeling that the release_task() issue would be much more
cleanly handled by just letting schedule_tail() do the last "put_task()",
the same way we handle the pending MM issue..
Maybe the best approach is to really mix the two approaches: a separate
clone flag to say that the parent really doesn't care about waiting for
the thing, but do it this way (so that init doesn't have to spend time
cleaning up either).
Linus
-
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/