From: "Stéphan Gorget" <sgorget@fb.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>, Jeethu Rao <jeethu@fb.com>,
"David S . Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@fb.com>,
Eric Dumazet <edumazet@google.com>, <kernel-team@fb.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] tcp: export drops counter to /proc/net/tcp{,6}
Date: Fri, 18 Aug 2017 13:50:50 +0100 [thread overview]
Message-ID: <11f30e3f-b08f-373e-b952-4a5bdedc3e7d@fb.com> (raw)
In-Reply-To: <1503058444.4936.169.camel@edumazet-glaptop3.roam.corp.google.com>
On 8/18/17 1:14 PM, Eric Dumazet wrote:
> On Fri, 2017-08-18 at 03:21 -0700, Stéphan Gorget wrote:
>> Those counters are exported for raw and udp but not for tcp, though they
>> are incremented.
>>
>> An example where it is useful is chasing listen overflow. Listen overflow
>> are counted as a global counter in LINUX_MIB_LISTENOVERFLOWS accessible
>> in /proc/net/netstat but there is no way to find related drops in the
>> information exported for tcp. With this patch it will make possible to
>> correlate growth of LINUX_MIB_LISTENOVERFLOWS with growth of drops for
>> a tcp socket.
>
> Simply use iproute2/ss tool to access this information in a very
> efficient way (like filtering done in the kernel, instead having to
> parse a gigantic /proc output)
>
> lpaa5:~# ss -tm state listening src :22
Thanks for the quick response, I'll use ss with those options that's
exactly what I needed.
prev parent reply other threads:[~2017-08-18 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 10:21 [PATCH net-next] tcp: export drops counter to /proc/net/tcp{,6} Stéphan Gorget
2017-08-18 12:14 ` Eric Dumazet
2017-08-18 12:50 ` Stéphan Gorget [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=11f30e3f-b08f-373e-b952-4a5bdedc3e7d@fb.com \
--to=sgorget@fb.com \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jeethu@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).