public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: DPC vs tasklet
Date: Fri, 21 May 2004 09:46:11 +0200	[thread overview]
Message-ID: <1085125571.2781.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <OFD20B05A9.954B29CD-ON85256E9B.0002C560-88256E9B.000355CC@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

On Fri, 2004-05-21 at 02:36, Bryan Henderson wrote:
> > Some
> > of the LINUX documentation I've read states "tasklets are the preferred
> > mechanism with which to implement your bottom half for a normal hardware
> > device".
> 
> In all the great answers about why other things are better than tasklets, 
> the basic question of why this documentation doesn't agree isn't 
> addressed.  Let me try:  I believe the context of this statement is a 
> comparison to the more traditional Unix method of implementing the bottom 
> half in the interrupt handler.  The statement is saying that a tasklet is 
> normally preferred to putting the same processing right in the interrupt 
> handler.
> 
> But in at least some cases, a kernel thread is better than either of 
> those.

yup. And the scsi driver case is special because the SCSI layer
implements the tasklet/softirq *for you* already, so instead of each
driver having to do it's own, just use the scsi one (by completing
directly in the ISR, which queues for the generic scsi softirq)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-05-21  7:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 16:52 DPC vs tasklet Infante, Jon
2004-05-20 17:03 ` 'Christoph Hellwig'
2004-05-20 17:08 ` Jeff Garzik
2004-05-21  0:36   ` Bryan Henderson
2004-05-21  0:39     ` Matthew Wilcox
2004-05-21  7:46     ` Arjan van de Ven [this message]
2004-05-20 17:20 ` Arjan van de Ven
2004-05-20 17:57   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 18:14 Infante, Jon

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=1085125571.2781.3.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=hbryan@us.ibm.com \
    --cc=linux-scsi@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