Date: Tue, 15 Jun 2004 14:14:40 -0500
From: Dean Nelson <dcn@sgi.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au, dcn@sgi.com
Subject: Re: calling kthread_create() from interrupt thread
Message-ID: <20040615191440.GA17669@sgi.com>
References: <40CF350B.mailxD2X1NPFBC@aqua.americas.sgi.com> <1087321777.2710.43.camel@laptop.fenrus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1087321777.2710.43.camel@laptop.fenrus.com>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1011
Lines: 27

On Tue, Jun 15, 2004 at 07:49:37PM +0200, Arjan van de Ven wrote:
> 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

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?

Thanks,
Dean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/