All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Josh Hunt <johunt@akamai.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] ss: add option to print socket information on one line
Date: Thu, 25 Apr 2019 16:53:08 -0700	[thread overview]
Message-ID: <f6fd56a3-f8e9-f60e-398c-9abe32a65b67@gmail.com> (raw)
In-Reply-To: <20190425155951.26d91cc6@hermes.lan>



On 4/25/19 3:59 PM, Stephen Hemminger wrote:

> I agree with this, but probably time to give ss a json output as well.

Yes, this might be quite nice.

(Although I am not sure of what extra cpu costs would be involved,
 when dealing with million of sockets per dump)
 

  parent reply	other threads:[~2019-04-25 23:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 21:21 [PATCH iproute2-next] ss: add option to print socket information on one line Josh Hunt
2019-04-25 22:59 ` Stephen Hemminger
2019-04-25 23:50   ` Josh Hunt
2019-04-25 23:53   ` Eric Dumazet [this message]
2019-04-30 18:30 ` David Ahern
2019-04-30 18:31   ` Josh Hunt
2019-04-30 18:55     ` Josh Hunt
2019-04-30 19:41       ` David Ahern
2019-04-30 19:42         ` Josh Hunt

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=f6fd56a3-f8e9-f60e-398c-9abe32a65b67@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=johunt@akamai.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.