From: Ramin Alidousti <ramin@UU.NET>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Why SFQ does not drops packets
Date: Fri, 01 Jun 2001 20:35:38 +0000 [thread overview]
Message-ID: <marc-lartc-99142783520485@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99138592919119@msgid-missing>
On Fri, Jun 01, 2001 at 11:23:46PM +0300, Serguei I. Ivantsov wrote:
> Hello Ramin,
>
> Well, let's perfom a little calculation :)
>
> "tc -s class ls dev eth0" :
>
> > class cbq 10:200 parent 10:1 leaf 8026: rate 16Kbit (bounded,isolated) prio 5
> > Sent 4049872 bytes 3846 pkts (dropped 0, overlimits 10286)
> > borrowed 0 overactions 1364 avgidle 309677 undertime 0
>
> after 4 second :
>
> > class cbq 10:200 parent 10:1 leaf 8026: rate 16Kbit (bounded,isolated) prio 5
> > Sent 4049926 bytes 3847 pkts (dropped 0, overlimits 10286)
> > rate 13bps
> > borrowed 0 overactions 1364 avgidle 309677 undertime 0
>
> 4049926(bytes)-4049872(bytes)T(bytes)
>
> 54(bytes)/4(second)\x13.5 BYTES PER SECOND!
I agree. This is how the *throughput* is measured. What I meant was
when you talk about Ethernet, Fast-Ethernet, Gig-Ethernet, TokenRing,
DS3, OC3, OC48, OC192... all is expressed in bits/sec and that's
the bandwidth. The throughput can be packets/sec or bytes/sec or
bits/sec.
Ramin
>
> It is easy to come to this conclusion when looking at MRTG graps.
>
> --
> Best regards,
> Serguei mailto:admin@gsc-game.kiev.ua
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-06-01 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 8:58 [LARTC] Why SFQ does not drops packets Serguei I. Ivantsov
2001-06-01 15:58 ` Wingtung.Leung
2001-06-01 17:41 ` Ethy H. Brito
2001-06-01 17:41 ` Ramin Alidousti
2001-06-01 19:57 ` Re[2]: " Serguei I. Ivantsov
2001-06-01 20:23 ` Serguei I. Ivantsov
2001-06-01 20:35 ` Ramin Alidousti [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=marc-lartc-99142783520485@msgid-missing \
--to=ramin@uu.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.