From: Andrew Morton <akpm@digeo.com>
To: Martin Diehl <lists@mdiehl.de>
Cc: rusty@rustcorp.com.au, neilb@cse.unsw.edu.au,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add module_kernel_thread for threads that live in modules.
Date: Mon, 16 Jun 2003 01:19:19 -0700 [thread overview]
Message-ID: <20030616011919.009b1c93.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306160907470.2079-100000@notebook.home.mdiehl.de>
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.
next prev parent reply other threads:[~2003-06-16 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 6:50 Rusty Russell
2003-06-16 7:58 ` Martin Diehl
2003-06-16 8:09 ` Rusty Russell
2003-06-16 8:57 ` Martin Diehl
2003-06-16 9:22 ` Rusty Russell
2003-06-16 10:27 ` Martin Diehl
2003-06-17 1:11 ` Rusty Russell
2003-06-16 8:19 ` Andrew Morton [this message]
2003-06-16 23:10 ` Neil Brown
2003-06-17 4:25 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-06-05 2:30 NeilBrown
2003-06-05 14:50 ` Andrey Klochko
2003-06-07 5:33 ` Neil Brown
2003-06-09 16:20 ` Andrey Klochko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030616011919.009b1c93.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--cc=neilb@cse.unsw.edu.au \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®