From: Juergen Pfeiffer <j.pfeiffer@seskion.de>
To: linux-kernel@vger.kernel.org
Subject: long disable of Softirqs in br_forward_delay_timer_expired()
Date: Thu, 18 Jan 2007 14:44:14 +0100 [thread overview]
Message-ID: <45AF79AE.1060102@seskion.de> (raw)
Hi
I had problems in my implementation of Profibus-protocol, because my
FDL-State machine is implemented in tasklets and
sometimes there were situations, where Soft-Irqs were disabled for
20-40mS (Coldfire 5485 / 96MHz).
After inserting some testpoints in kernels source, doing dump_stack(),
when the jiffie-time get longer then 20mS,
i detected the place of the long Soft-Irq disable in function
static void br_forward_delay_timer_expired(..)
inside file "net/bridge/br_stp_timer.c"
It does a
spin_lock_bh(..);
... some functionality;
spin_unlock_bh(..);
Does anybody know, why the functionality inbetween lock/unlock takes so long
(2-4 jiffies @ HZ=100)
Thank You
Juergen Pfeiffer,
Seskion GmbH
Karlsruher Str. 11/1
70771 Leinfelden-Echterdingen
Germany
j.pfeiffer@seskion.de
www.seskion.de
next reply other threads:[~2007-01-18 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 13:44 Juergen Pfeiffer [this message]
2007-01-19 9:35 ` long disable of Softirqs in br_forward_delay_timer_expired() Juergen Pfeiffer
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=45AF79AE.1060102@seskion.de \
--to=j.pfeiffer@seskion.de \
--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