From: Markus Elfring <Markus.Elfring@web.de>
To: David Miller <davem@davemloft.net>,
David Ahern <dsahern@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: Josh Hunt <johunt@akamai.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ss: Checking efficient analysis for network connections
Date: Sun, 2 Jun 2019 07:40:49 +0200 [thread overview]
Message-ID: <e1af968b-199b-a0f2-dbb1-c294aceeb08c@web.de> (raw)
In-Reply-To: <20190601.164838.1496580524715275443.davem@davemloft.net>
> If you use netlink operations directly,
Thanks for such feedback.
Should this programming interface become better known?
> you can have the kernel filter on various criteria
> and only get the socket entries you are interested in.
This is good to know.
> This whole discussion has zero to do with what text format 'ss' outputs.
Some software components are affected here.
The socket statistic tool is using data from the directory “/proc/net”.
* Provided text files refer to known Linux data formats.
Can it happen to work with other data formats there?
* The analysis program can also be extended for the support
of additional data formats, can't it?
Regards,
Markus
next prev parent reply other threads:[~2019-06-02 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1556674718-5081-1-git-send-email-johunt@akamai.com>
2019-05-30 9:11 ` [PATCH v2] ss: add option to print socket information on one line Markus Elfring
2019-06-01 8:36 ` ss: Checking efficient analysis for network connections Markus Elfring
2019-06-01 23:48 ` David Miller
2019-06-02 5:40 ` Markus Elfring [this message]
2019-06-13 14:40 ` Markus Elfring
2019-07-23 8:25 ` Markus Elfring
2019-09-16 10:32 ` ss: Checking selected network ports Markus Elfring
2019-10-22 6:00 ` [RFC] " Markus Elfring
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=e1af968b-199b-a0f2-dbb1-c294aceeb08c@web.de \
--to=markus.elfring@web.de \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=johunt@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).