mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mroth@calpoly.edu
To: jjs@lexus.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Spawning kernel threads from other kernel threads(?)
Date: Tue, 20 Nov 2001 18:37:01 -0800	[thread overview]
Message-ID: <H000060409379e23.1006310106.davinci.artisan.calpoly.edu@MHS> (raw)

>>and BTW what is an "?entity?" ?

Oops. Excuse my ambiguity. When I said "entity" I was describing the design in
a very general form. Let me phrase it like this; my software in theory looks
like:

- a manager "entity" is responsible for destroying and creating "worker"
threads.
- the worker threads then perform a specific tasks.

That's theory though. The implementation actually looks like:

A linux kernel thread has the responsibility of creating and killing threads
(thus 
termed "manager").
The worker threads (also kernel threads) perform specific tasks.

>>2.4.3 is awfully stale for starters -

Yup. This is not by choice :-) The hardware/OS is pretty much fixed at this
point.

Would spawning a kernel thread from a kernel thread work with a recent kernel?

>>cu

>>jjs

> 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



             reply	other threads:[~2001-11-21  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21  2:37 mroth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-21  1:41 mroth
2001-11-21  1:51 ` J Sloan

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=H000060409379e23.1006310106.davinci.artisan.calpoly.edu@MHS \
    --to=mroth@calpoly.edu \
    --cc=jjs@lexus.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®