From: "Daniel Glöckner" <dg@emlix.com>
To: linux-rt-users@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Issue with sched-no-work-when-pi-blocked.patch
Date: Wed, 29 Aug 2012 18:04:58 +0200 [thread overview]
Message-ID: <503E3DAA.10309@emlix.com> (raw)
Hi,
on a system running 3.2.23-rt37 the boot time is increased by two
minutes because of commit 4b03ee27 (sched-no-work-when-pi-blocked.patch)
when booting with ip=dhcp. This is due to ic_open_devs taking rtnl_mutex
before it ups the network interfaces. The ndo_open function then calls
netif_carrier_off which queues a work that as well takes rtnl_mutex. This
stalls the workqueue (tsk_is_pi_blocked()) and prevents phy_state_machine
and thus netif_carrier_on from being run. ic_open_devs waits for two minutes
for a link before it gives up and releases rtnl_mutex.
So, what is the rationale behind sched-no-work-when-pi-blocked.patch?
On the other hand, I think I'll just drop rtnl_mutex in ic_open_devs
while it is waiting for a link.
Daniel
--
Dipl.-Math. Daniel Glöckner, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax +49 551 30664-11,
Bertha-von-Suttner-Straße 9, 37085 Göttingen, Germany
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
Geschäftsführer: Dr. Uwe Kracke, Ust-IdNr.: DE 205 198 055
emlix - your embedded linux partner
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2012-08-29 16:13 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=503E3DAA.10309@emlix.com \
--to=dg@emlix.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.