From: Ville Nummela <ville.nummela@mail.necsom.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Linus Torvalds <torvalds@transmeta.com>,
Ville Nummela <ville.nummela@mail.necsom.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: tasklets in 2.4.6
Date: 09 Jul 2001 12:09:44 +0300 [thread overview]
Message-ID: <7aelrqxycn.fsf@necsom.com> (raw)
In-Reply-To: <7an16iy2wa.fsf@necsom.com> <3B4563D5.89A1ACA3@mandrakesoft.com> <3B45760D.6F99149C@mandrakesoft.com>
In-Reply-To: <3B45760D.6F99149C@mandrakesoft.com> (Jeff Garzik's message of "Fri, 06 Jul 2001 04:25:49 -0400")
Jeff Garzik <jgarzik@mandrakesoft.com> writes:
> Jeff Garzik wrote:
> > The only thing that appears fishy is that if the tasklet constantly
> > reschedules itself, it will never leave the loop AFAICS. This affects
> > tasklet_hi_action as well as tasklet_action.
> As I hacked around to fix this, I noticed Andrea's ksoftirq patch
> already fixed this. So, I decided to look over his patch instead.
I tried that patch too, but with not so good results: The code LOOKS good to
mee too, but for some reason it still seems to stuck in looping the tasklet
code only. btw. I'm trying this on PPC, it might have something to do with
that.. :)
I'll try to hack this out :-/
--
| ville.nummela@necsom.com tel: +358-40-8480344
| So Linus, what are we doing tonight?
| The same thing we every night Tux. Try to take over the world!
next prev parent reply other threads:[~2001-07-09 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 6:42 tasklets in 2.4.6 Ville Nummela
2001-07-06 7:08 ` Jeff Garzik
2001-07-06 8:25 ` Jeff Garzik
2001-07-06 8:27 ` Jeff Garzik
2001-07-06 11:57 ` Andrea Arcangeli
2001-07-06 12:07 ` Jeff Garzik
2001-07-09 9:09 ` Ville Nummela [this message]
2001-07-09 11:39 ` Ville Nummela
2001-07-09 14:24 ` Andrea Arcangeli
2001-07-06 11:28 ` Andrea Arcangeli
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=7aelrqxycn.fsf@necsom.com \
--to=ville.nummela@mail.necsom.com \
--cc=andrea@suse.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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