public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Dean Nelson <dcn@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: calling kthread_create() from interrupt thread
Date: Tue, 15 Jun 2004 22:41:04 +0200	[thread overview]
Message-ID: <m38yeolfkv.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <27qxQ-67a-27@gated-at.bofh.it> (Dean Nelson's message of "Tue, 15 Jun 2004 20:10:10 +0200")

Dean Nelson <dcn@sgi.com> writes:
>
> As mentioned above, it is possible for this "simple" function to sleep/block
> for an indefinite period of time. I was under the impression that one
> couldn't block a work queue thread for an indefinite period of time. Am
> I mistaken?

You could create your own work queue upfront. Blocking an generic workqueue 
for a long time is indeed nasty.

-Andi


       reply	other threads:[~2004-06-15 20:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2004-06-15 17:42 calling kthread_create() from interrupt thread Dean Nelson
2004-06-15 17:49 ` Arjan van de Ven
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

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=m38yeolfkv.fsf@averell.firstfloor.org \
    --to=ak@muc.de \
    --cc=dcn@sgi.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