From: "Manfred Spraul" <manfred@colorfullife.com>
To: <sampsa@netsonic.fi>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Performance is weird (fwd)
Date: Thu, 15 Mar 2001 19:08:03 +0100 [thread overview]
Message-ID: <005b01c0ad7c$00274f20$5517fea9@local> (raw)
One difference between idle and a running user space app is that the
kernel->user space return path checks for pending softirqs, but the ide
thread doesn't.
Perhaps cpu_idle() should also check for pending softirq's before
hlt'ing?
idle thread is running.
* hw interrupt
* * hw interrupt handler
* * * packet arrives
* * * softirq marked
* * hw interrupt handler returns
* do_softirq
* * net_rx called
* * * an hw interrupt interrupts net_rx
* * * * a second packet arrives, softirq marked again.
* * * hw interrupt returns
* * net_rx returns
* do_softirq notices that net_rx is queued again, but doesn't process
it immediately (otherwise it would cause an endless loop)
* hw interrupt returns
idle thread sleeps again.
!! one packet is waiting unprocessed
What about adding if(softirq_active...) do_softirq() into default_idle?
--
Manfred
next reply other threads:[~2001-03-15 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 18:08 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-15 19:58 Performance is weird (fwd) Manfred Spraul
2001-03-15 15:25 Sampsa Ranta
2001-03-24 12:42 ` Sampsa Ranta
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='005b01c0ad7c$00274f20$5517fea9@local' \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sampsa@netsonic.fi \
/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