From: Krzysztof Witkowski <Krzysztof.Witkowski@mobile.put.edu.pl>
To: linux-can@vger.kernel.org
Subject: CPU load inhibits CAN interrupts
Date: Tue, 10 Apr 2012 16:40:14 +0200 [thread overview]
Message-ID: <4F84464E.7030403@mobile.put.edu.pl> (raw)
I have an Ubuntu box with 3.2 kernel, CPU with 2 cores and PEAK-PCI card
(SJA1000 controller attached via PCI bus)
I'm testing receive capabilities of the card on 1Mbit network using
peak_pci module. It can handle about ~4000 packets per second, the
corresponding interrupt is also raised ~4000 times per second (as
/proc/interrupts shows) and it does not cause high CPU load on the system.
However, if I generate artificial CPU load with stress command:
chrt --idle 0 stress -c 2
the Receive Interrupts from SJA1000 are no longer raised at all and
therefore no messages are received. At the same time network card (e100)
on the same IRQ is working properly.
Why CPU load inhibits hardware interrupts and what can be done about it?
Or should I suspect hardware malfunction?
next reply other threads:[~2012-04-10 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 14:40 Krzysztof Witkowski [this message]
2012-04-10 17:48 ` CPU load inhibits CAN interrupts Wolfgang Grandegger
2012-04-11 9:40 ` Krzysztof Witkowski
2012-04-11 13:23 ` Wolfgang Grandegger
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=4F84464E.7030403@mobile.put.edu.pl \
--to=krzysztof.witkowski@mobile.put.edu.pl \
--cc=linux-can@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