netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Christian Hesse <mail@eworm.de>
Subject: Re: [PATCH 1/1] ip-link: allow human readable output with base of 1024 only for byte counts
Date: Mon, 30 Mar 2015 09:03:15 +0200	[thread overview]
Message-ID: <20150330090315.68ce923d@leda.localdomain> (raw)
In-Reply-To: <20150329225835.2cf0f770@uryu.home.lan>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

Stephen Hemminger <stephen@networkplumber.org> on Sun, 2015/03/29 22:58:
> On Thu, 26 Mar 2015 12:24:08 +0100
> Christian Hesse <list@eworm.de> wrote:
> 
> > From: Christian Hesse <mail@eworm.de>
> > 
> > Counting bytes with a base of 1024 is ok. Counting packets, errors, etc
> > that way makes no sense.
> > So only print byte counts with a base of 1024 if option -iec is given.
> > 
> > Signed-off-by: Christian Hesse <mail@eworm.de>
> 
> This changes the output which users expect, especially the packet counts
> should follow existing practice. And I doubt anyone would have 1024 errors.

With current code you can give -iec and everything (including errors) is
printed with IEC units. This patch changes it to only print byte counts with
IEC units, so error will be displayed with a base of 1000 always.

I think my patch changes things to what user expects, no?
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Chris           get my mail address:    */=0;b=c[a++];)
putchar(b-1/(/*               gcc -o sig sig.c && ./sig    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-03-30  7:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 11:24 [PATCH 1/1] ip-link: allow human readable output with base of 1024 only for byte counts Christian Hesse
2015-03-30  5:58 ` Stephen Hemminger
2015-03-30  7:03   ` Christian Hesse [this message]

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=20150330090315.68ce923d@leda.localdomain \
    --to=list@eworm.de \
    --cc=mail@eworm.de \
    --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).