From: Daniel Borkmann <dborkman@redhat.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: Vadim Kochan <vadim4j@gmail.com>, netdev <netdev@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH iproute2 3/3] ss: Unify tcp stats output
Date: Tue, 20 Jan 2015 12:17:03 +0100 [thread overview]
Message-ID: <54BE392F.2070804@redhat.com> (raw)
In-Reply-To: <CAPh34mdi+8wLaUY3ZBks40wbOtdzsbTrmuvsHivRouc9rs3gig@mail.gmail.com>
Hi Hagen,
On 01/20/2015 11:29 AM, Hagen Paul Pfeifer wrote:
> On 18 January 2015 at 21:43, Vadim Kochan <vadim4j@gmail.com> wrote:
...
> My proposal:
>
> 1) support grouping. E.g. DCTCP could be separated in the following
> manner. I.e. "dctcp:[ ce_state: %d, alpha: %d, ... ]" or
> "dctcp:ce_state.%d;alpha,%d" like the socket memory output.
> This makes it easier for humans and scripts to parse the output.
> Since some time ss output is extended really extensive (especially
> Eric make use of this). This is not the end and additional values are
> added - make the current babylon even worse.
I have no strong opinion on this, but I also have a limited view on
what applications try to parse ss output in general.
As mentioned, for human readability, we should implement a top-like
display option which is allowed to have a rather 'instable' output
by nature and levels of detail can be folded/unfolded on demand.
> 2) add a JSON formater as soon as possible to make the output
> parseable. I would do this - it is required anyway.
Given the recent discussion on web10g, json output option might
be very useful to provide i.e. when stats are being further extended.
Cheers,
Daniel
next prev parent reply other threads:[~2015-01-20 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 20:43 [PATCH iproute2 0/3] Unify output for inet sockets Vadim Kochan
2015-01-18 20:43 ` [PATCH iproute2 1/3] ss: Make meminfo look little bit more readable Vadim Kochan
2015-01-18 20:43 ` [PATCH iproute2 2/3] ss: Unify inet sockets output Vadim Kochan
2015-01-18 20:43 ` [PATCH iproute2 3/3] ss: Unify tcp stats output Vadim Kochan
2015-01-19 13:57 ` Hagen Paul Pfeifer
2015-01-19 14:04 ` Vadim Kochan
2015-01-19 14:28 ` Hagen Paul Pfeifer
2015-01-19 14:28 ` Vadim Kochan
2015-01-19 15:01 ` Hagen Paul Pfeifer
2015-01-19 14:48 ` Daniel Borkmann
2015-01-19 14:50 ` Vadim Kochan
2015-01-20 10:29 ` Hagen Paul Pfeifer
2015-01-20 10:52 ` Vadim Kochan
2015-01-20 11:06 ` Vadim Kochan
2015-01-20 11:17 ` Daniel Borkmann [this message]
2015-01-20 11:09 ` Vadim Kochan
2015-01-20 11:43 ` Hagen Paul Pfeifer
2015-01-20 18:36 ` Cong Wang
2015-01-21 8:54 ` Hagen Paul Pfeifer
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=54BE392F.2070804@redhat.com \
--to=dborkman@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vadim4j@gmail.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).