All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:41:52 +0000	[thread overview]
Message-ID: <marc-lartc-99141739420863@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99138592919119@msgid-missing>

On Fri, Jun 01, 2001 at 02:41:47PM -0300, Ethy H. Brito wrote:

> On Fri, 1 Jun 2001, Wingtung.Leung wrote:
> 
> > On Fri, 1 Jun 2001, Serguei I. Ivantsov wrote:
> >
> > > Please explain me why my class 10:300 does not drops packets?
> > > My class is bounded and isolated - but 8kbit!\x1783bps!!!
> > >
> > >
> > > class cbq 10:300 parent 10:1 leaf 801b: rate 8Kbit (bounded,isolated) prio 5
> > >  Sent 470737 bytes 388 pkts (dropped 0, overlimits 7465)
> > >  rate 1783bps 1pps backlog 40p
> > >   borrowed 0 overactions 290 avgidle -786633 undertime 612289
> >
> > I'm not sure what 1783bps means. If it is "bytes/sec" more packets should
> > be dropped, if it is "bits/sec", everything seems to be ok.
> 
> As a general rule "bps" means bits per second and "Bps" means bytes per second.
> I am not shure if it applies here. I should say it does.

Usually, when one talks about the bandwidth it always refers to "bit"
not "byte".

Ramin


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-06-01 17:41 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 [this message]
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

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-99141739420863@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.