Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andreas Hasenack <ahasenack@terra.com.br>
To: lartc@vger.kernel.org
Subject: [LARTC] 1k: 1000 or 1024?
Date: Thu, 23 Feb 2006 17:12:30 +0000	[thread overview]
Message-ID: <20060223171230.GI3411@mandriva.com> (raw)

The docs[1][2] suggest it's 1024, but tc says something else:

# tc qdisc add dev eth0 root tbf rate 1kbps latency 50ms burst 1500

# tc -s qdisc ls dev eth0
qdisc tbf 8009: rate 8000bit burst 1499b lat 48.8ms
                     ^^^^^^^
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
 rate 0bit 0pps backlog 0b 0p requeues 0



If 1k were 1024, then I would have 8192bit above.


1. http://www.docum.org/docum.org/faq/cache/74.html
2.http://ds9a.nl/2.4Networking/howto/lartc.qdisc.html#LARTC.QDISC.EXPLAIN

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-02-23 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 17:12 Andreas Hasenack [this message]
2006-02-24  3:35 ` [LARTC] 1k: 1000 or 1024? gypsy

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=20060223171230.GI3411@mandriva.com \
    --to=ahasenack@terra.com.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox