Martin Diehl <lists@mdiehl.de> wrote:
>
> > create_thread would use keventd to start the thread, and stop_thread
> > would tell keventd to set should_die, wmb(), wake it up, and
> > sys_wait() for it.
> >
> > Thoughts?
> > Rusty.
>
> Why using keventd?
keventd knows how to clean up children, handle SIGCHLD, etc. That code was
hard-won.
And kernel threads which are parented by userspace processes tend to
accidentally inherit things we'd rather they didn't. daemonize() and
reparent_to_init() try to fix things up, but I'm still not sure we got it
all.
Using keventd will tend to prevent mistakes.
-
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/
This archive was generated by hypermail 2b29 : Mon Jun 23 2003 - 22:00:17 EST