mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Dean Nelson <dcn@sgi.com>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: calling kthread_create() from interrupt thread
Date: Tue, 15 Jun 2004 19:49:37 +0200	[thread overview]
Message-ID: <1087321777.2710.43.camel@laptop.fenrus.com> (raw)
In-Reply-To: <40CF350B.mailxD2X1NPFBC@aqua.americas.sgi.com>

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

On Tue, 2004-06-15 at 19:42, Dean Nelson wrote:
> I'm working on a driver that needs to create threads that can sleep/block
> for an indefinite period of time.
> 
>     . Can kthread_create() be called from an interrupt handler?

no

> 
>     . Is the cost of a kthread's creation/demise low enough so that one
>       can, as often as needed, create a kthread that performs a simple
>       function and exits?  Or is the cost too high for this?

for that we have keventd in 2.4, work queues in 2.6


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-15 17:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 17:42 Dean Nelson
2004-06-15 17:49 ` Arjan van de Ven [this message]
2004-06-15 18:05   ` Dean Nelson
2004-06-15 18:14     ` Jesse Barnes
2004-06-15 22:14       ` Jeff Garzik
2004-06-15 18:15     ` Richard B. Johnson
2004-06-15 19:01       ` Robin Holt
2004-06-15 19:28         ` Roland Dreier
2004-06-15 19:30         ` Chris Wright
2004-06-15 23:40         ` Rusty Russell
2004-06-15 19:14   ` Dean Nelson
2004-06-15 19:27     ` Roland Dreier
2004-06-15 19:59     ` Chris Wright
     [not found] <27qex-5LX-17@gated-at.bofh.it>
     [not found] ` <27qoT-5Uy-15@gated-at.bofh.it>
     [not found]   ` <27qxQ-67a-27@gated-at.bofh.it>
2004-06-15 20:41     ` Andi Kleen

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=1087321777.2710.43.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=dcn@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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®