linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: du <duzhenhuan@gmail.com>
To: linux-can@vger.kernel.org
Subject: Re: socketcan receive queue too many frames
Date: Wed, 27 Mar 2013 12:01:25 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130327T125524-733@post.gmane.org> (raw)
In-Reply-To: 5152DCF2.80804@pengutronix.de

Marc Kleine-Budde <mkl <at> pengutronix.de> writes:


> 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.


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?




  reply	other threads:[~2013-03-27 12:01 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 [this message]
2013-03-27 12:04     ` Marc Kleine-Budde

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=loom.20130327T125524-733@post.gmane.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).