From: Marc Kleine-Budde <mkl@pengutronix.de>
To: du <duzhenhuan@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: socketcan receive queue too many frames
Date: Wed, 27 Mar 2013 13:04:45 +0100 [thread overview]
Message-ID: <5152E05D.80908@pengutronix.de> (raw)
In-Reply-To: <loom.20130327T125524-733@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
On 03/27/2013 01:01 PM, du wrote:
>> What is "socketcan buffer"?
> sorry ,I means socketcan only.
:)
>> What kind of CAN frame do you get? Maybe error messages, due to the open
>> bus?
> It's not error message , just normal CAN data frames.
Okay.
> I thought it may has something to do with buffer.
> If my application is not fast enough to read the frames in buffer,
> I can still get frames even the bus is open, is it right?
Yes, socketcan is designed not to drop any messages, but it will, if the
rx-queue (between kernel and your apps) gets to lange. If you receive
frames in your application 10 seconds after you disconnected the cable
you have a serious design or performance problem (or both) in you system.
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: 263 bytes --]
prev parent reply other threads:[~2013-03-27 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 11:38 socketcan receive queue too many frames du
2013-03-27 11:50 ` Marc Kleine-Budde
2013-03-27 12:01 ` du
2013-03-27 12:04 ` Marc Kleine-Budde [this message]
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=5152E05D.80908@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=duzhenhuan@gmail.com \
--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.