public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dragan Stancevic <visitor@xalien.org>
To: linux-kernel@vger.kernel.org
Subject: tasklet broken? Quick question
Date: Thu, 31 Jan 2002 19:20:01 -0800	[thread overview]
Message-ID: <200202010320.g113K2m02524@linux.xalien.org> (raw)

Hi,

I am seeing a strange behavior when using tasklets so I was wondering if 
this is a bug or a feature and if anyone else has experienced the same 
behavior.

I am using 2.4.9 and I checked the ChangeLog and there was a fix from Andrea 
in 2.4.8 with relation to tasklets but nothing after that.

I schedule a tasklet from a network driver interrupt and what I am seeing is 
that in some cases the tasklet runs twice when I am expecting it to run once.

Here is pseudo code how it looks like:

network_interrupt(){
	tasklet_schedule()
}

tasklet_code(){
	do_stuff()
}

and here is what happens:

I get an interrupt which calls tasklet_schedule, the tasklet starts executing 
and has not exited yet and I get another interrupt that calls 
tasklet_schedule, now the tasklet code exits but in some cases it executes 
again without ever tasklet_schedule being called again, I checked this is 
done on the same cpu as the interrupt was called so thats ok. I am just not 
sure if I should be expecting that "extra" execution, I thought I shouldn't.


PS: Please Cc me on reply as I am not currently on lkml. Thanks.


-- 
Peace can only come as a natural consequence
of universal enlightenment. -Dr. Nikola Tesla

                 reply	other threads:[~2002-02-01  3:36 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=200202010320.g113K2m02524@linux.xalien.org \
    --to=visitor@xalien.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox