From: Denys Fedoryschenko <denys@visp.net.lb>
To: netdev@vger.kernel.org
Subject: iproute2 / tbf with large burst seems broken again
Date: Mon, 24 Aug 2009 15:07:13 +0300 [thread overview]
Message-ID: <200908241507.13504.denys@visp.net.lb> (raw)
Seems something related to the changes with resolution. I remember something
like this happened before, and i report about it, but i am not able to find
in mail archives. It seems packets queueing and not passing shaper, if burst
is set to large value.
Kernel 2.6.30.4 was ok.
uname -a
Linux PPPoE_146 2.6.31-rc7-build-0046-32bit #6 SMP Sun Aug 23 03:51:14 EEST
2009 i686 GNU/Linux
PPPoE_146 ~ # tc -s -d qdisc show dev ppp87;sleep 10;tc -s -d qdisc show dev
ppp87
qdisc prio 1: root bands 3 priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Sent 47980 bytes 367 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 357p requeues 0
qdisc tbf 2: parent 1:1 rate 96000bit burst 2000Kb/8 mpu 0b lat 500.0ms
Sent 47580 bytes 357 pkt (dropped 0, overlimits 376 requeues 0)
rate 384bit 1pps backlog 0b 357p requeues 0
qdisc tbf 3: parent 1:2 rate 1024Kbit burst 2000Kb/8 mpu 0b lat 500.0ms
Sent 400 bytes 10 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc ingress ffff: parent ffff:fff1 ----------------
Sent 21342 bytes 347 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc prio 1: root bands 3 priomap 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Sent 48410 bytes 372 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 362p requeues 0
qdisc tbf 2: parent 1:1 rate 96000bit burst 2000Kb/8 mpu 0b lat 500.0ms
Sent 48010 bytes 362 pkt (dropped 0, overlimits 381 requeues 0)
rate 448bit 1pps backlog 0b 362p requeues 0
qdisc tbf 3: parent 1:2 rate 1024Kbit burst 2000Kb/8 mpu 0b lat 500.0ms
Sent 400 bytes 10 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc ingress ffff: parent ffff:fff1 ----------------
Sent 21692 bytes 352 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
PPPoE_146 ~ # cat /proc/net/psched
000003e8 00000040 000f4240 3b9aca00
next reply other threads:[~2009-08-24 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 12:07 Denys Fedoryschenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-24 23:37 iproute2 / tbf with large burst seems broken again Denys Fedoryschenko
2009-08-25 6:22 ` Jarek Poplawski
2009-08-25 7:34 ` Denys Fedoryschenko
2009-08-25 8:43 ` Jarek Poplawski
2009-08-25 9:00 ` Jarek Poplawski
2009-08-25 9:41 ` Jarek Poplawski
2009-08-25 10:29 ` Denys Fedoryschenko
2009-08-25 11:16 ` Denys Fedoryschenko
2009-08-25 12:13 ` Jarek Poplawski
2009-08-25 12:18 ` Denys Fedoryschenko
2009-08-25 20:03 ` Jarek Poplawski
2009-08-26 19:03 ` Jarek Poplawski
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=200908241507.13504.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@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.