From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Socket drop count
Date: Thu, 24 Sep 2020 12:52:30 +0200 [thread overview]
Message-ID: <b69de361-db52-2eef-c41e-bc9ac0a6222d@pengutronix.de> (raw)
In-Reply-To: <dada7073-7c21-4705-58e4-da80cdc1249e@grandegger.com>
[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]
On 9/24/20 12:19 PM, Wolfgang Grandegger wrote:
>
> Am 24.09.20 um 11:53 schrieb Marc Kleine-Budde:
>> On 9/24/20 11:41 AM, Wolfgang Grandegger wrote:
>>> Hello,
>>>
>>> candump can monitor the count of dropped RX messages if the socket
>>> buffer if full with the option "-d". Is there also a command to list
>>> that drop count of a certain socket, e.g. "ss"?
>>
>> I haven't tested it, but what about "ss -m"
>>
>>> -m, --memory
>>> Show socket memory usage. The output format is:
>>>
>>> skmem:(r<rmem_alloc>,rb<rcv_buf>,t<wmem_alloc>,tb<snd_buf>,
>>> f<fwd_alloc>,w<wmem_queued>,o<opt_mem>,
>>> bl<back_log>,d<sock_drop>)
>
> Hm, the TCP sockets report such a line but I cannot find my CAN socket
> in there opened by "candump":
>
> # ss -p| grep candump
>
> "ss" seams not (yet) to support "AF_CAN" sockets :(.
Looks like a patch opportunity :D
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-24 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 9:41 Socket drop count Wolfgang Grandegger
2020-09-24 9:53 ` Marc Kleine-Budde
2020-09-24 10:19 ` Wolfgang Grandegger
2020-09-24 10:52 ` Marc Kleine-Budde [this message]
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=b69de361-db52-2eef-c41e-bc9ac0a6222d@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=wg@grandegger.com \
/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).