linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Ssagarr Patil <hugarsagar@outlook.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: C_CAN: can frame drops
Date: Wed, 23 Jul 2014 18:04:52 +0200	[thread overview]
Message-ID: <53CFDD24.3070004@hartkopp.net> (raw)
In-Reply-To: <BAY176-W240BDB3FFF425370BF5B47D3FE0@phx.gbl>

Hello Sagar,

generally dropping CAN frames on driver level is a complete different problem
in opposite to dropping CAN frames on socket receive level.

A drop on the socket layer usually occurs, when the application does not get
enough CPU time to read and process the CAN frames. But drops on CAN driver
layer lead to a possible resource problem on your system.

Can you tell a bit more about your platform (hardware, CPU, cpu clock, RAM)
and Linux Kernel version?

Regards,
Oliver


On 23.07.2014 16:48, Ssagarr Patil wrote:
> Hi,
> 
> I am using the c_can driver for latest kernel and using the latest canutils to dump to a file.
> My can bus is set at a rate of 1Mb (receiving 7000fps bus load of 80%).
> 
> When I use the candump tool to dump can frames I get following message,
> 
> 'DROPCOUNT: dropped 2223 CAN frames on 'any' socket (total drops 1629092)'
> 
> SO to solve this problem if I use the -r option of candump and tried 
> candump any -d -e -r 999999999 -l
> 
> If I do this the can frames are dropped in the driver ie I see 
> this c_can_handle_lost_msg_obj() function being called frequently in which can frame
> is overwritten.
> 
> How to solve this issue any pointers would be helpful.
> 
> Thanks,
> --Sagar
>  		 	   		  --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2014-07-23 16:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 14:48 C_CAN: can frame drops Ssagarr Patil
2014-07-23 16:04 ` Oliver Hartkopp [this message]
2014-07-23 16:33   ` Ssagarr Patil
2014-07-24  7:40     ` Ssagarr Patil
2014-07-24 18:09       ` Oliver Hartkopp
2014-07-25  8:20         ` Ssagarr Patil
2014-07-25  7:17 ` Marc Kleine-Budde
2014-07-25  8:13   ` Ssagarr Patil
2014-07-25  8:16     ` Marc Kleine-Budde
2014-07-25  8:22       ` Ssagarr Patil
2014-07-25  8:27         ` Marc Kleine-Budde
2014-07-25  8:35           ` Ssagarr Patil
2014-07-25  8:48             ` Marc Kleine-Budde
2014-07-25  9:47               ` Ssagarr Patil
2014-07-25 10:10                 ` Marc Kleine-Budde
2014-07-25 11:22                   ` Ssagarr Patil
2014-07-25 10:43                 ` Oliver Hartkopp
2014-07-25 11:24                   ` Ssagarr Patil
2014-07-30 11:28                   ` Prabhakar Lad
2014-07-30 16:17                     ` Oliver Hartkopp
2014-07-31 12:41                       ` Ssagarr Patil
2014-07-31 12:42                         ` Marc Kleine-Budde
2014-07-31 14:11                           ` Oliver Hartkopp
2014-07-31 14:19                             ` Prabhakar Lad
2014-12-18  9:41                               ` [RFC] sched policies for candump Oliver Hartkopp
2014-12-18 12:33                                 ` Prabhakar Lad
2014-12-18 13:51                                   ` Oliver Hartkopp

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=53CFDD24.3070004@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=hugarsagar@outlook.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).