From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Kicinski Subject: Re: [PATCH iproute2 net-next 0/3] ss: Allow selection of columns to be displayed Date: Thu, 1 Nov 2018 14:06:23 -0700 Message-ID: <20181101140623.4d6211a0@cakuba.netronome.com> References: <7ffc00c8-bdf6-5c75-564e-2663494bda5d@gmail.com> <20181030183420.181b3d51@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Stefano Brivio , "Yoann P." , Stephen Hemminger , netdev@vger.kernel.org To: David Ahern Return-path: Received: from mx4.wp.pl ([212.77.101.12]:23617 "EHLO mx4.wp.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725780AbeKBGLI (ORCPT ); Fri, 2 Nov 2018 02:11:08 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 31 Oct 2018 20:48:05 -0600, David Ahern wrote: > > spacing with a special character in the format string, that is: > > > > "%S.%Qr.%Qs %Al:%Pl %Ar:%Pr %p\n" > > > > would mean "align everything to the right, distribute remaining > > whitespace between %S, %Qr and %Qs". But it looks rather complicated > > at a glance. > > > > My concern here is that once this goes in for 1 command, the others in > iproute2 need to follow suit - meaning same syntax style for all > commands. Given that I'd prefer we get a reasonable consensus on syntax > that will work across commands -- ss, ip, tc. If it is as simple as > column names with a fixed order, that is fine but just give proper > consideration given the impact. FWIW I just started piping iproute2 commands to jq. Example: tc -s -j qdisc show dev em1 | \ jq -r '.[] | [.kind,.parent,.handle,.offloaded,.bytes,.packets,.drops,.overlimits,.requeues,.backlog,.qlen,.marked] | @tsv' JSONification would probably be quite an undertaking for ss :(