From: Rusty Russell <rusty@rustcorp.com.au>
To: NeilBrown <neilb@cse.unsw.edu.au>
Cc: 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 16:50:33 +1000 [thread overview]
Message-ID: <20030616065058.D1C9E2C08A@lists.samba.org> (raw)
Hi Neil,
There are several problems with this patch. Ignoring the fact
that you use __module_get. Firstly, you bump the module count
permentantly while the thread is running: how does it ever get
unloaded? Secondly, modprobe becomes your parent.
There have been ambitious attempts to do a nice "thread
creation and stopping" interface before. Given the delicate logic
involved in shutting threads down, I think this makes sense. Maybe
something like:
/* Struct which identifies a kernel thread, handed to creator and
thread. */
struct kthread
{
int pid;
int should_die; /* Thread should exit when this is set. */
/* User supplied arg... */
void *arg;
};
struct kthread *create_thread(int (*fn)(struct kthread*), void *arg,
unsigned long flags,
const char *namefmt, ...);
void cleanup_thread(struct kthread *);
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.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next reply other threads:[~2003-06-16 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 6:50 Rusty Russell [this message]
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
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=20030616065058.D1C9E2C08A@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.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®