From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: Steffen Rose <ro@emtas.de>, linux-can@vger.kernel.org
Subject: Re: unsure - socketCAN blocking
Date: Mon, 08 Oct 2012 17:00:02 +0200 [thread overview]
Message-ID: <5072EA72.9050308@pengutronix.de> (raw)
In-Reply-To: <5072E9A5.2060908@grandegger.com>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On 10/08/2012 04:56 PM, Wolfgang Grandegger wrote:
>>> Your program probably produces CAN frames faster than they could be
>>> delivered by your CAN hardware. Your choices are:
>>
>> I'm unsure.
>> My CPU load is high. My application polling is not optimal at the moment. But
>> the CAN busload is not so high.
>>
>> At the moment I would think, it is more a problem internal or on USB. I'm
>> unsure. I search information to analyze the current situation.
>>
>>> 2) Increase txqueue length to 10000 or so.
>>> (ifconfig can0 txqueuelen 10000)
>>
>> I did it.
>>
>> after a little bit time...
>
> Did it run longer than before? Anyway, the candump utility shows how to
> count messages dropped because the queue was full. Search for the option
> "-d".
>
>>
>> Now my error:
>> write: Interrupted system call
>
> Hm, who has interrupted the write system call? gdb?
Is your application making use of signals? This is not an error, just
restart the write.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-10-08 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 10:16 unsure - socketCAN blocking Steffen Rose
2012-10-08 11:46 ` Marc Kleine-Budde
2012-10-08 14:36 ` Steffen Rose
2012-10-08 14:56 ` Wolfgang Grandegger
2012-10-08 15:00 ` Marc Kleine-Budde [this message]
2012-10-08 15:21 ` Steffen Rose
2012-10-08 15:19 ` Steffen Rose
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=5072EA72.9050308@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=ro@emtas.de \
--cc=wg@grandegger.com \
/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.