From: Maksim Krasnyanskiy <maxk@qualcomm.com>
To: kuznet@ms2.inr.ac.ru
Cc: andrea@suse.de, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, mingo@redhat.com,
davem@redhat.com (Dave Miller)
Subject: Re: [PATCH] [IMPORTANT] Re: 2.4.7 softirq incorrectness.
Date: Mon, 30 Jul 2001 11:32:11 -0700 [thread overview]
Message-ID: <4.3.1.0.20010730110208.05e62260@mail1> (raw)
In-Reply-To: <200107281741.VAA12995@ms2.inr.ac.ru>
In-Reply-To: <4.3.1.0.20010727141716.05651ac0@mail1>
> > tasklet_schedule calls tasklet_unlock after it schedules tasklet,
>
>Hmm... but this opens one more bug: are schedules not lost, when
>they are made while tasklet is running ?
Yes it does.
btw Here is an idea. May be we should reschedule tasklet on the same cpu it's running on.
It should probably improve cache usage and stuff.
I'm thinking about something like this.
static inline void tasklet_schedule(struct tasklet_struct *t)
{
if (test_bit(TASKLET_STATE_RUN, &t->state)) {
set_bit(TASKLET_NEED_RESCHED, &t->state);
} else if (!test_and_set_bit(TASKLET_STATE_SCHED, &t->state)) {
int cpu = smp_processor_id();
unsigned long flags;
local_irq_save(flags);
t->next = tasklet_vec[cpu].list;
tasklet_vec[cpu].list = t;
cpu_raise_softirq(cpu, TASKLET_SOFTIRQ);
local_irq_restore(flags);
}
}
static void tasklet_action(struct softirq_action *a)
{
int cpu = smp_processor_id();
struct tasklet_struct *list;
local_irq_disable();
list = tasklet_vec[cpu].list;
tasklet_vec[cpu].list = NULL;
local_irq_enable();
while (list) {
struct tasklet_struct *t = list;
list = list->next;
if (tasklet_trylock(t)) {
if (!atomic_read(&t->count)) {
if (!test_and_clear_bit(TASKLET_STATE_SCHED, &t->state))
BUG();
t->func(t->data);
tasklet_unlock(t);
if (test_and_clear_bit(TASKLET_NEED_RESCHED, &t->state)
goto resched;
continue;
}
tasklet_unlock(t);
}
resched:
local_irq_disable();
t->next = tasklet_vec[cpu].list;
tasklet_vec[cpu].list = t;
cpu_raise_softirq(cpu, TASKLET_SOFTIRQ);
local_irq_enable();
}
}
There is small window there but this is just rfc. So if tasklet is already running we set NEED_RESCHED bit and tasklet_action
reschedules tasklet on the same cpu. (currently we may reschedule it on anther cpu).
Comments ?
Max
Maksim Krasnyanskiy
Senior Kernel Engineer
Qualcomm Incorporated
maxk@qualcomm.com
http://bluez.sf.net
http://vtun.sf.net
next prev parent reply other threads:[~2001-07-30 18:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 20:44 Rusty Russell
2001-07-22 23:34 ` Andrea Arcangeli
2001-07-23 9:06 ` Rusty Russell
2001-07-23 14:29 ` Andrea Arcangeli
2001-07-24 9:35 ` Rusty Russell
2001-07-25 19:33 ` Andrea Arcangeli
2001-07-26 20:26 ` Rusty Russell
2001-07-23 9:25 ` Kai Germaschewski
2001-07-23 11:12 ` Jeff Garzik
2001-07-23 14:18 ` Andrea Arcangeli
2001-07-23 12:05 ` David S. Miller
2001-07-23 14:31 ` Andrea Arcangeli
2001-07-23 22:24 ` Alexey Kuznetsov
2001-07-25 22:23 ` Andrea Arcangeli
2001-07-26 17:46 ` kuznet
2001-07-26 18:03 ` Jeff Garzik
2001-07-26 18:29 ` Andrea Arcangeli
2001-07-27 16:48 ` kuznet
2001-07-27 18:31 ` Maksim Krasnyanskiy
2001-07-27 18:59 ` kuznet
2001-07-27 19:21 ` Maksim Krasnyanskiy
2001-07-27 19:35 ` kuznet
2001-07-28 0:52 ` [PATCH] [IMPORTANT] " Maksim Krasnyanskiy
2001-07-28 17:41 ` kuznet
2001-07-28 18:02 ` Andrea Arcangeli
2001-07-28 19:02 ` kuznet
2001-07-28 19:32 ` Andrea Arcangeli
2001-07-28 23:28 ` Alexey Kuznetsov
2001-07-29 17:07 ` Linus Torvalds
2001-07-29 17:52 ` kuznet
2001-07-30 18:50 ` Ingo Molnar
2001-07-30 22:47 ` Nigel Gamble
2001-07-30 22:56 ` Christoph Hellwig
2001-07-31 18:08 ` kuznet
2001-07-28 17:54 ` Andrea Arcangeli
2001-07-28 19:17 ` Andrea Arcangeli
2001-07-30 18:32 ` Maksim Krasnyanskiy [this message]
2001-07-27 0:47 ` Maksim Krasnyanskiy
2001-07-27 15:01 ` Andrea Arcangeli
2001-07-27 9:34 ` David S. Miller
2001-07-27 17:01 ` kuznet
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=4.3.1.0.20010730110208.05e62260@mail1 \
--to=maxk@qualcomm.com \
--cc=andrea@suse.de \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@transmeta.com \
/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®