public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@lvl7•com>
To: Khai Trinh <kqtrinh@yahoo•com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: tasklets and waking up sleeping process question
Date: Thu, 11 Jul 2002 19:38:09 -0400	[thread overview]
Message-ID: <3D2E16E1.3080602@lvl7.com> (raw)
In-Reply-To: 20020711224210.62434.qmail@web11505.mail.yahoo.com


You _can_ do either.  Doing the later however, is more or less re-inventing the
wheel, as the tasklet mechanism is designed specifically so that you can do non
time-sensitive interrupt work (the tasklet runs in interrupt context, but with
interrupts still enabled).  So going to the trouble to create a kernel thread to
  pend on a semaphore to be unlocked by an interrupt handler top-half really
never makes sense, unless you need to be able to move your driver code between a
linux environment and a non-linux environment which doesn't have the concept of
tasklets.  Even then, I'd still suggest that you put your code together in such
a way that when building for linux you use tasklets rather than a whole new
kernel thread.
Hope that helps!
Neil

Khai Trinh wrote:

> I have new to Linux. I am reading the Linux device
> driver book second eddition and am trying to make some
> sense out of it.
>
> I am trying to implement an interrupt handler. From
> the description in the book, it seems that one can go
> about implementing the bottom half either using the
> tasklets method or by waking up a sleeping process in
> the top half interrupt handler.
>
> Is what I understood correct or I am totally of the
> topics?
>
> When do you determine which method to implement for an
> interrupt handler?
>
> Regards,
> --Khai
>
>
>


--
/******************************************************************
*Neil Horman
*Software Engineer
*LVL7 Systems
*13000 Weston Pkwy.
*Cary, NC 27513
*(919)-865-2915
*nhorman@lvl7•com
*PGP keyID 0xB5E1020A
*http://www.keyserver.net/en
*******************************************************************/


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-07-11 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11 22:42 tasklets and waking up sleeping process question Khai Trinh
2002-07-11 23:38 ` Neil Horman [this message]

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=3D2E16E1.3080602@lvl7.com \
    --to=nhorman@lvl7$(echo .)com \
    --cc=kqtrinh@yahoo$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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