From: Markus Elfring <Markus.Elfring@web.de>
To: Josh Hunt <johunt@akamai.com>, David Ahern <dsahern@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: ss: Checking efficient analysis for network connections
Date: Sat, 1 Jun 2019 10:36:40 +0200 [thread overview]
Message-ID: <3d1c67c8-7dfe-905b-4548-dae23592edc5@web.de> (raw)
In-Reply-To: <1556674718-5081-1-git-send-email-johunt@akamai.com>
> Multi-line output in ss makes it difficult to search for things with grep.
I became more concerned about efficient data processing for the
provided information. There are further software development possibilities
to consider, aren't there?
The chosen data formats influence the software situation considerably.
* Information is exported together with extra space characters.
Other field delimiters can occasionally be nicer.
* Regular expressions are useful to extract data from text lines.
But other programming interfaces are safer to work with data structures.
The mentioned program can be used to filter the provided input.
But if you would like to work with information from the filtered records,
you would need to repeat some data processing by the calling process
so that items will be converted into structured elements.
Would you like to avoid duplicate work?
I imagine then that it would be also nicer to perform filtering based on
configurable constraints at the data source directly.
How much can Linux help more in this software area?
How do you think about such ideas?
Regards,
Markus
next prev parent reply other threads:[~2019-06-01 8:37 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 ` Markus Elfring [this message]
2019-06-01 23:48 ` ss: Checking efficient analysis for network connections David Miller
2019-06-02 5:40 ` Markus Elfring
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=3d1c67c8-7dfe-905b-4548-dae23592edc5@web.de \
--to=markus.elfring@web.de \
--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
all inboxes | Powered by JetHome®