From: Wolfgang Grandegger <wg@grandegger.com>
To: Krzysztof Witkowski <Krzysztof.Witkowski@mobile.put.edu.pl>
Cc: linux-can@vger.kernel.org
Subject: Re: CPU load inhibits CAN interrupts
Date: Tue, 10 Apr 2012 19:48:03 +0200 [thread overview]
Message-ID: <4F847253.5080507@grandegger.com> (raw)
In-Reply-To: <4F84464E.7030403@mobile.put.edu.pl>
On 04/10/2012 04:40 PM, Krzysztof Witkowski wrote:
> 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
What does "-c 2" do? My "chrt" command does not have that option.
> 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.
That's wired. Interrupt processing of the SJA1000 is done in the
interrupt context.
> Why CPU load inhibits hardware interrupts and what can be done about it?
Hm, what does "ip -d -s can0" report while you are producing CPU load
with the stress command above.
> Or should I suspect hardware malfunction?
More likely it's a bug.
Wolfgang.
next prev parent reply other threads:[~2012-04-10 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 14:40 CPU load inhibits CAN interrupts Krzysztof Witkowski
2012-04-10 17:48 ` Wolfgang Grandegger [this message]
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=4F847253.5080507@grandegger.com \
--to=wg@grandegger.com \
--cc=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 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.