From: Juergen Quade <quade@hsnr.de>
To: J S <webnews@comcast.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Tasklets vs. Task Queues for Deferred Processing
Date: Sat, 29 Mar 2003 09:12:51 +0100 [thread overview]
Message-ID: <20030329081251.GA6604@hsnr.de> (raw)
In-Reply-To: <1048893277.4058.11.camel@localhost.localdomain>
On Fri, Mar 28, 2003 at 06:14:37PM -0500, J S wrote:
> I'm trying to defer some processing to a later point. I'm in a softirq,
> so in_interrupt() returns true. I need to schedule some work for later,
> in process context. I have read in the O'Reilly linux device drivers
> book that tasklets always run in interrupt time. Also, I guess the only
> task_queue that is in process context is the scheduler task queue. I've
> seen in a few places that task queues are on their way out and tasklets
> are being used instead. Is this completely true? Should I consider
True.
> task queues as a deprecated method of deferred processing?` What other
> deferred processing methods can I use that will run in process context?
Beside application triggered driver functions (open, close, read,
write ...) you can (only) use kernel threads.
You can use "pure" kernel threads, workqueues or especially the
kevent-daemon (2.4.x) or the event-workqueue (2.5.x).
If you only need to call something like a short function, use
the work queue. Need more info?
Juergen.
next prev parent reply other threads:[~2003-03-29 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 23:14 Tasklets vs. Task Queues for Deferred Processing J S
2003-03-29 8:12 ` Juergen Quade [this message]
2003-03-29 8:12 ` Duncan Sands
2003-03-29 21:48 ` Jonathan Corbet
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=20030329081251.GA6604@hsnr.de \
--to=quade@hsnr.de \
--cc=linux-kernel@vger.kernel.org \
--cc=webnews@comcast.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.