mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Dean Nelson <dcn@sgi.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: calling kthread_create() from interrupt thread
Date: Tue, 15 Jun 2004 12:59:47 -0700	[thread overview]
Message-ID: <20040615125947.A22989@build.pdx.osdl.net> (raw)
In-Reply-To: <20040615191440.GA17669@sgi.com>; from dcn@sgi.com on Tue, Jun 15, 2004 at 02:14:40PM -0500

* Dean Nelson (dcn@sgi.com) wrote:
> Can an interrupt handler setup a work_struct structure, call schedule_work()
> and then simply return, not waiting around for the work queue event to
> complete?

Yes, that's a fundamental feature.  However, it's not so nice to use the
generic events workqueue for really long sleeping work since it can stall
the entire queue.  You might consider your own queue.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2004-06-15 20:02 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
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 [this message]
     [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=20040615125947.A22989@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=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®