From: George Anzinger <george@mvista.com>
To: "Kristian Lyngstøl" <nesquik@bohemians.org>
Cc: "Christian Kögler" <christian.koegler@unibw-muenchen.de>,
linux-kernel@vger.kernel.org
Subject: Re: tasklets vs. workqueues
Date: Thu, 19 Feb 2004 14:44:57 -0800 [thread overview]
Message-ID: <40353C69.2030509@mvista.com> (raw)
In-Reply-To: <20040217014123.GA16165@bohemians.org>
Kristian Lyngstøl wrote:
> On Mon, Feb 16, 2004 at 08:20:31PM +0100, Christian Kögler wrote:
>
>>When should I use tasklets and when should I user workqueues?
>>What are the differences?
>
>
> To quote "Linux Kernel Development" (Which I am currently reading):
>
> Work queues defer work into a kernel thread-the work always runs in process
> context. Most importantly, work queues are schedulable and can therefore sleep.
>
> Normally, there is little decision between work queues or sotftirqs/tasklets.
> If the deferred work need to sleep, work queues are used. If the deferred
> work need not sleepa, softirqs or tasklets are used.
Being in process context, you can also change the priority and schedule policy
as needed to fit your application, while you are rather stuck with tasklets in
this regard.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2004-02-21 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 19:20 tasklets vs. workqueues Christian Kögler
2004-02-17 1:41 ` Kristian Lyngstøl
2004-02-19 22:44 ` George Anzinger [this message]
[not found] <Pine.LNX.4.44.0402210140160.1775-100000@notebook.home.mdiehl.de>
2004-02-25 18:56 ` George Anzinger
2004-02-25 21:11 ` Martin Diehl
2004-02-25 21:58 ` George Anzinger
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=40353C69.2030509@mvista.com \
--to=george@mvista.com \
--cc=christian.koegler@unibw-muenchen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nesquik@bohemians.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