From: "Serguei I. Ivantsov" <manowar@gsc-game.kiev.ua>
To: lartc@vger.kernel.org
Subject: [LARTC] Why SFQ does not drops packets
Date: Fri, 01 Jun 2001 08:58:49 +0000 [thread overview]
Message-ID: <marc-lartc-99138592919119@msgid-missing> (raw)
Hello All!
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
--
Regards,
Serguei I. Ivantsov
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-06-01 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 8:58 Serguei I. Ivantsov [this message]
2001-06-01 15:58 ` [LARTC] Why SFQ does not drops packets 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
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-99138592919119@msgid-missing \
--to=manowar@gsc-game.kiev.ua \
--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