From: J Sloan <jjs@lexus.com>
To: mroth@calpoly.edu
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Spawning kernel threads from other kernel threads(?)
Date: Tue, 20 Nov 2001 17:51:46 -0800 [thread overview]
Message-ID: <3BFB08B2.3AE5BF60@lexus.com> (raw)
In-Reply-To: <H00006040937765d.1006306811.davinci.artisan.calpoly.edu@MHS>
mroth@calpoly.edu wrote:
> Question:
> Can you spawn a kernel thread from another kernel thread? I want to
> have one manager ?entity? which will dynamically create kernel threads as
> needed. Right now, when I try to spawn another thread from the manager ?entity?
> [as of today, still a kernel thread] it will crash. Is this legal? If not, what
> is the alternative?
>
> kernel_thread()
> Kernel Version 2.4.3
2.4.3 is awfully stale for starters -
and BTW what is an "?entity?" ?
cu
jjs
next prev parent reply other threads:[~2001-11-21 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 1:41 Spawning kernel threads from other kernel threads(?) mroth
2001-11-21 1:51 ` J Sloan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 2:37 mroth
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=3BFB08B2.3AE5BF60@lexus.com \
--to=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroth@calpoly.edu \
/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