From: DervishD <lartc@dervishd.net>
To: lartc@vger.kernel.org
Subject: [LARTC] About "b" meaning "byte" and bit
Date: Fri, 31 Aug 2007 16:26:24 +0000 [thread overview]
Message-ID: <20070831162624.GA6133@DervishD> (raw)
Hi all :)
I think that this issue has already been discussed on this list, but
google didn't find anything interesting, so I'm bringing the subject
again.
The output of "tc" uses "b" meaning "byte" and "bit" for "bit". The
"official" suffixes for those units are "B" and "b", respectively, and
on top of this, I'm not sure if "kbit" means "kilobit" or "kibibit" in
"tc" output.
I haven't had time to look at iproute2 sources, so I don't know if
this should be dealt with in iproute2 or in the kernel itself. Most of
the kernel has switched to SI units already, and IMHO most of the utils
should do the same, to avoid the endless problem of SI vs. binary units.
This said, maybe this weird syntas is used in tc so third party apps
can parse the output. These apps certainly will break if a change in the
syntax is made, but otherwise I see no reason to keep using "b" instead
of "B" and "bit" instead of "b". Currently the only way of having a sane
syntax (and not only regarding units...) is "tcng"·
If such a modification is seen as appropriate, I volunteer to make
the patch.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-08-31 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 16:26 DervishD [this message]
2007-09-03 4:33 ` [LARTC] About "b" meaning "byte" and bit Indunil Jayasooriya
2007-09-03 9:17 ` DervishD
2007-09-06 21:14 ` Andy Furniss
2007-09-07 7:34 ` DervishD
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=20070831162624.GA6133@DervishD \
--to=lartc@dervishd.net \
--cc=lartc@vger.kernel.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.