linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Martin Kozusky <mkozusky@kkmicro.cz>
Cc: linux-can@vger.kernel.org
Subject: Re: can4linux compilation for i.mx25 under 2.6.39
Date: Wed, 30 May 2012 14:40:37 +0200	[thread overview]
Message-ID: <4FC61545.2020504@pengutronix.de> (raw)
In-Reply-To: <jq53rt$uqu$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

On 05/30/2012 02:29 PM, Martin Kozusky wrote:
>> Have you debugged which component is dropping frames? Is it the hardware
>> or the socket because your application is to slow?
> 
> I tried to solve this 19.4.2012 (thread "CAN messages being lost on
> i.MX25 with flexcan") and when I changed rcvbuf_size to 10000000 it

Oh, I see, this conversation slipped my mind.

> helped, but still sometimes few CAN frames are dropped (and many more
> when I try to write to SD card or internal flash). So I think it's not
> HW problem.
> The best for me would be some kernel module which would just put the CAN
> frame into some big "from userspace available" buffer in the interrupt
> and nothing more. My app would check if there is anything new and read
> it out.
> There are around 1500/sec (at 250kbit) can frames on the bus when the
> problem arise, I think it's not that much.

Are you writing the can frames to storage in the same thread as
receiving them?

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: 262 bytes --]

  reply	other threads:[~2012-05-30 12:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 11:39 can4linux compilation for i.mx25 under 2.6.39 Martin Kozusky
2012-05-30 11:50 ` Marc Kleine-Budde
2012-05-30 12:05   ` Martin Kozusky
2012-05-30 12:08     ` Martin Kozusky
2012-05-30 12:18       ` Marc Kleine-Budde
2012-05-30 12:34         ` Martin Kozusky
2012-05-30 12:37           ` Marc Kleine-Budde
2012-05-30 12:16     ` Marc Kleine-Budde
2012-05-30 12:29       ` Martin Kozusky
2012-05-30 12:40         ` Marc Kleine-Budde [this message]
2012-05-30 12:50           ` Martin Kozusky
2012-05-30 13:18             ` Marc Kleine-Budde
2012-05-30 13:26               ` Martin Kozusky
2012-05-30 14:18                 ` Marc Kleine-Budde
2012-05-31 13:29                   ` Martin Kozusky
2012-05-31 13:42                     ` Marc Kleine-Budde
2012-05-31 16:28                       ` Oliver Hartkopp
2012-06-01  8:12                         ` Martin Kozusky
2012-06-01 11:22                           ` Oliver Hartkopp
2012-06-01  6:19                       ` Martin Kozusky

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=4FC61545.2020504@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkozusky@kkmicro.cz \
    /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).