From: Wolfgang Grandegger <wg@grandegger.com>
To: Ernast Sevo <ersevs@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: command ip -details -statistics link show wlan0
Date: Thu, 16 May 2013 09:02:03 +0200 [thread overview]
Message-ID: <5194846B.1070307@grandegger.com> (raw)
In-Reply-To: <CAOD0pe=EMt3+ymJMwT+gOUbFZN7_R8exkh36G5457O61GoV4UA@mail.gmail.com>
Hi Ernast,
On 05/15/2013 08:58 PM, Ernast Sevo wrote:
> Hello,
>
> I am quite new to socket can and I had a question about the output of
> the command: ip -details -statistics link show can0. When I run the
> above command I get the following output:
>
> re-started bus-errors arbit-lost error-warn error-pass bus-off
> 0 0 0 0 0 0
> RX: bytes packets errors dropped overrun mcast
> 3956387 948121 11 0 11 0
> TX: bytes packets errors dropped carrier collsns
> 100 44 0 0 0 0
>
>
> I see that I received 11 errors packets (all of them being rx overrun
> errors) and that no packets were dropped. Does the dropped field refer
> to packets lost in userspace (i.e because they weren't being read fast
> enough and the socket receive buffer overflowed) or does the dropped
> packet field refer to dropped packets being dropped somewhere other
> than userspace?
They refer to packets dropped in the driver for some reason, maily
because memory is short (ENOMEM). The overrun errors above are reported
by the hardware due to messages arrived but there was no space to store
it. Messages dropped because the socket buffer was full can be reported
with the candump option "-d" as shown here:
https://gitorious.org/linux-can/can-utils/blobs/master/candump.c#line549
Hope that helps.
Wolfgang.
next prev parent reply other threads:[~2013-05-16 7:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 18:58 command ip -details -statistics link show wlan0 Ernast Sevo
2013-05-16 7:02 ` Wolfgang Grandegger [this message]
[not found] ` <CAOD0pekopW9g0SD=BnOMCEp3SdVZPrx5jY_CKLjZV09sWepS6A@mail.gmail.com>
2013-05-16 13:43 ` Ernast Sevo
2013-05-16 13:45 ` Marc Kleine-Budde
[not found] ` <5194F46D.4060905@grandegger.com>
2013-05-16 15:32 ` Ernast Sevo
2013-05-16 15:37 ` Marc Kleine-Budde
2013-05-16 15:43 ` Wolfgang Grandegger
2013-05-16 16:37 ` Ernast Sevo
[not found] ` <CAOD0pekym7Ey1eRn-ndwjEnsJUpf84xHbexztpRBjUKqoaGcPw@mail.gmail.com>
[not found] ` <51B239EA.6060603@grandegger.com>
2013-06-08 7:42 ` Wolfgang Grandegger
2013-06-10 12:53 ` Ernast Sevo
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=5194846B.1070307@grandegger.com \
--to=wg@grandegger.com \
--cc=ersevs@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).