From: Rusty Russell <rusty@rustcorp.com.au>
To: Martin Diehl <lists@mdiehl.de>
Cc: NeilBrown <neilb@cse.unsw.edu.au>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
akpm@zip.com.au
Subject: Re: [PATCH] Add module_kernel_thread for threads that live in modules.
Date: Mon, 16 Jun 2003 18:09:23 +1000 [thread overview]
Message-ID: <20030616082925.AF5EE2C0D2@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 16 Jun 2003 09:58:43 +0200." <Pine.LNX.4.44.0306160907470.2079-100000@notebook.home.mdiehl.de>
In message <Pine.LNX.4.44.0306160907470.2079-100000@notebook.home.mdiehl.de> you write:
> Why using keventd? Personally I'd prefer a synchronous thread start/stop,
> particularly with the thread living in a module.
> Maybe some generalisation of:
It would be syncronous: but doing kernel_thread yourself means trying
to clean up using daemonize et al, which is incomplete and always
makes me nervous.
An implementation detail to users, but IMHO an important one.
Also, this replaces complete_and_exit: the thread can just exit. This
simplifies things for the users, too...
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-06-16 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 6:50 [PATCH] Add module_kernel_thread for threads that live in modules Rusty Russell
2003-06-16 7:58 ` Martin Diehl
2003-06-16 8:09 ` Rusty Russell [this message]
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=20030616082925.AF5EE2C0D2@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--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