From: Stephen Hemminger <stephen@networkplumber.org>
To: Craig Gallek <kraig@google.com>
Cc: netdev@vger.kernel.org, edumazet@google.com
Subject: Re: [PATCH iproute2 v2] ss: Include -E option for socket destroy events
Date: Fri, 26 Jun 2015 00:21:00 -0400 [thread overview]
Message-ID: <20150626002100.7eff28d0@uryu.home.lan> (raw)
In-Reply-To: <1434554088-10200-1-git-send-email-kraig@google.com>
On Wed, 17 Jun 2015 11:14:48 -0400
Craig Gallek <kraig@google.com> wrote:
> Use the IPv4/IPv6/TCP/UDP multicast groups of NETLINK_SOCK_DIAG
> to filter and display socket statistics as they are destroyed.
>
> Kernel support patch series: 24029a3603cfa633e8bc2b3fb3e48e76c497831d
>
> Signed-off-by: Craig Gallek <kraig@google.com>
Accepted. Currently sitting on local net-next branch until after merge.
prev parent reply other threads:[~2015-06-26 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 15:14 [PATCH iproute2 v2] ss: Include -E option for socket destroy events Craig Gallek
2015-06-26 4:21 ` Stephen Hemminger [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=20150626002100.7eff28d0@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=edumazet@google.com \
--cc=kraig@google.com \
--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).