From: Marc Kleine-Budde <mkl@pengutronix.de>
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 15:45:16 +0200 [thread overview]
Message-ID: <5194E2EC.2050804@pengutronix.de> (raw)
In-Reply-To: <CAOD0pekNvW1Vh7KkHGffNyxGh=RTe+2cHdZwO-q6VDfPV6z_dQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On 05/16/2013 03:43 PM, Ernast Sevo wrote:
> That definitely clears things up a bit. One more question though. Does
> the number in
> overrun or the number in errors from the command above then directly
> refer to the number
> of packets lost on the hardware level due to there being no space to
> store it (i.e 11 overrun or
> errors means 11 packets lost) ?
This depends on the hardware/driver. But usually that means 11 overrun
events, which means _at_least_ 11 CAN frames lost.
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 --]
next prev parent reply other threads:[~2013-05-16 13:45 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
[not found] ` <CAOD0pekopW9g0SD=BnOMCEp3SdVZPrx5jY_CKLjZV09sWepS6A@mail.gmail.com>
2013-05-16 13:43 ` Ernast Sevo
2013-05-16 13:45 ` Marc Kleine-Budde [this message]
[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=5194E2EC.2050804@pengutronix.de \
--to=mkl@pengutronix.de \
--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 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.