mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Fernandes <agnel.joel@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: tasklets and queuing.
Date: Sat, 10 Oct 2009 20:36:25 -0700	[thread overview]
Message-ID: <9ff7a3bc0910102036u6e912817hd335d41a5976f30b@mail.gmail.com> (raw)

Hi Friends,

I have a question about tasklets:

I understand that they are used to defer work during interrupt
handling. What I don't understand is - how do they handle queuing of
deferred work?
Specially with tasklets, if a tasklet is re-scheduled before the
previous scheduling of the same tasklet has a chance to run, then the
tasklet is executed only once - not twice. But what if the work that
the tasklet was supposed to do in these 2 instances were different and
that its function was supposed to be passed 2 different structures?
Shouldn't the tasklet be executed twice with these 2 structures?

I know that work queues are there for that, but how do device drivers
that use tasklets cope with the above?

Thanks,
-Joel

                 reply	other threads:[~2009-10-11  3:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9ff7a3bc0910102036u6e912817hd335d41a5976f30b@mail.gmail.com \
    --to=agnel.joel@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®