All of lore.kernel.org
 help / color / mirror / Atom feed
From: chuckw@ieee.org
To: linux-kernel@vger.kernel.org
Subject: Re: Looking for comments on Bottom-Half/Tasklet/SoftIRQ
Date: Sun, 19 Aug 2001 06:57:02 -0400	[thread overview]
Message-ID: <20010819065702.C2388@ieee.org> (raw)
In-Reply-To: <20010818231704.A2388@ieee.org> <3B7FF06A.4090606@fugmann.dhs.org> <20010819013508.B2388@ieee.org> <3B800CF9.9000606@fugmann.dhs.org>
In-Reply-To: <3B800CF9.9000606@fugmann.dhs.org>; from afu@fugmann.dhs.org on Sun, Aug 19, 2001 at 09:01:13PM +0200

Many thanks once again.

Chuck

On Sun, Aug 19, 2001 at 09:01:13PM +0200, Anders Peter Fugmann wrote:
> chuckw@ieee.org wrote:
> > Thanks
> > 
> > 	So, Bottom halves don't need to be re-entrant as do tasklets.  SoftIRQ's
> > need to be re-entrant.  The advantage of tasklets is that each tasklet can
> > be farmed out to different CPU's AND they don't need to be re-entrant 
> > because only one instance is allowed at a time.  I think I got it.
> 
> That is 100% correct.
> 
> > 
> > 	Could you direct me to some code in the kernel which uses tasklets
> > so I can see the inner workings?
> 
> Actually very few systems in the kernel has been rewritten to use 
> tasklets instead og BH's.
> 
> But as they are very simillar to BH's, you should be able to use the 
> same thinking, its just a new API.
> 
> Take a look at include/linux/interrupt.h
> (or http://lxr.linux.no/source/include/linux/interrupt.h, an invaluable 
> source when coding for linux).
> 
> Regards
> Anders Fugmann
> 

  reply	other threads:[~2001-08-19 22:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19  3:17 Looking for comments on Bottom-Half/Tasklet/SoftIRQ chuckw
2001-08-19 16:59 ` Anders Peter Fugmann
2001-08-19  5:35   ` chuckw
2001-08-19 19:01     ` Anders Peter Fugmann
2001-08-19 10:57       ` chuckw [this message]
2001-08-20 16:04     ` george anzinger
2001-08-20 12:39       ` chuckw
2001-08-20 21:05       ` Anders Peter Fugmann

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=20010819065702.C2388@ieee.org \
    --to=chuckw@ieee.org \
    --cc=linux-kernel@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 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.