From: "Denys" <denys@visp.net.lb>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2-2.6.20-070313 bug ?
Date: Thu, 22 Mar 2007 14:46:03 +0200 [thread overview]
Message-ID: <20070322124533.M79867@visp.net.lb> (raw)
In-Reply-To: <46026717.9060909@trash.net>
Dear Sir
Already i sent. I will copy here also
Normal "patched by me" iproute2
/sbin/tc qdisc del dev ppp0 root
/sbin/tc qdisc add dev ppp0 root handle 1: prio
/sbin/tc qdisc add dev ppp0 parent 1:1 handle 2: tbf buffer 1024kb latency
500ms rate 128kbit peakrate 256kbit minburst 16384
/sbin/tc filter add dev ppp0 parent 1:0 protocol ip prio 10 u32 match ip dst
0.0.0.0/0 flowid 2:1
tc(patched) monitor output
deleted qdisc prio 1: dev ppp0 root bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1
1 1 1 1
qdisc prio 1: dev ppp0 root bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc tbf 2: dev ppp0 parent 1:1 rate 128000bit burst 1024Kb peakrate
256000bit minburst 16Kb lat 500.0ms
filter dev ppp0 parent 1: protocol ip pref 10 u32 fh 800::800 order 2048 key
ht 800 bkt 0 flowid 2:1
match 00000000/00000000 at 16
VISP-Office ~ #cat /proc/net/psched
00000001 00000001 000f4240 000003e8
Now running tc2, it is "stock" version
/sbin/tc2 qdisc del dev ppp0 root
/sbin/tc2 qdisc add dev ppp0 root handle 1: prio
/sbin/tc2 qdisc add dev ppp0 parent 1:1 handle 2: tbf buffer 1024kb latency
500ms rate 128kbit peakrate 256kbit minburst 16384
/sbin/tc2 filter add dev ppp0 parent 1:0 protocol ip prio 10 u32 match ip dst
0.0.0.0/0 flowid 2:1
Monitor output:
deleted qdisc prio 1: dev ppp0 root bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1
1 1 1 1
qdisc prio 1: dev ppp0 root bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
qdisc tbf 2: dev ppp0 parent 1:1 rate 128000bit burst 1024Kb peakrate
256000bit minburst 16Kb lat 500.0ms
filter dev ppp0 parent 1: protocol ip pref 10 u32 fh 800::800 order 2048 key
ht 800 bkt 0 flowid 2:1
match 00000000/00000000 at 16
VISP-Office ~ #cat /proc/net/psched
00000001 00000001 000f4240 000003e8
Sure when i run tc2 - i see in stats, when it stopped (tc - normal, tc2 -
buggy):
VISP-Office ~ #tc -s qdisc show dev ppp0
qdisc ingress ffff: ----------------
Sent 184893 bytes 2311 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc prio 1: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 7765 bytes 64 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 64p requeues 0
qdisc tbf 2: parent 1:1 rate 128000bit burst 4294932937b peakrate 256000bit
minburst 16Kb lat 4.2s
Sent 7765 bytes 64 pkt (dropped 0, overlimits 64 requeues 0)
rate 0bit 0pps backlog 0b 64p requeues 0
VISP-Office ~ #tc2 -s qdisc show dev ppp0
qdisc ingress ffff: ----------------
Sent 186423 bytes 2324 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
qdisc prio 1: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 8677 bytes 77 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 77p requeues 0
qdisc tbf 2: parent 1:1 rate 128000bit burst 4294932937b peakrate 256000bit
minburst 16Kb lat 4.2s
Sent 8677 bytes 77 pkt (dropped 0, overlimits 77 requeues 0)
rate 0bit 0pps backlog 0b 77p requeues 0
I wish this will be enough information. Thanks for your help!
On Thu, 22 Mar 2007 12:23:03 +0100, Patrick McHardy wrote
> Denys wrote:
> > Possible i discovered bug, but maybe specific to my setup.
> >
> > In your sources (tc/tc_core.h) i notice
> > #define TIME_UNITS_PER_SEC 1000000000
> > When i change it to
> > #define TIME_UNITS_PER_SEC 1000000.0
> > (it was value before in sources)
> > everythign works fine. Otherwise tbf not working at all, it is dropping
all
> > packets.
> >
> > Did anyone test new iproute2 with tbf?
>
> Yes, please send the commands you use.
--
Virtual ISP S.A.L.
next prev parent reply other threads:[~2007-03-22 12:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 18:00 iproute2-2.6.20-070313 bug ? Denys
2007-03-22 11:23 ` Patrick McHardy
2007-03-22 12:46 ` Denys [this message]
2007-03-22 13:09 ` Patrick McHardy
[not found] ` <20070322131245.M85528@visp.net.lb>
2007-03-22 13:23 ` Patrick McHardy
2007-03-22 13:35 ` Denys
[not found] ` <20070322132637.M88445@visp.net.lb>
2007-03-22 13:43 ` Patrick McHardy
2007-03-22 13:47 ` Denys
2007-03-22 13:26 ` Denys
2007-03-22 17:12 ` Stephen Hemminger
2007-03-22 17:14 ` Patrick McHardy
2007-03-26 18:49 ` more... iproute2/htb/whatever critical " Denys
2007-03-27 15:10 ` Patrick McHardy
2007-03-27 15:18 ` Denys
2007-03-27 16:00 ` Denys
2007-03-27 16:21 ` Patrick McHardy
2007-03-28 17:38 ` another " Denys
2007-03-28 23:55 ` Denys
2007-03-29 10:58 ` Patrick McHardy
2007-03-31 2:26 ` more iproute2 issues (not critical) Denys
2007-03-31 2:31 ` Denys
2007-03-31 14:16 ` Patrick McHardy
2007-04-04 0:03 ` one more... iproute commands lockup whole system Denys
2007-04-04 1:10 ` jamal
2007-04-04 1:39 ` Patrick McHardy
2007-04-04 2:09 ` jamal
2007-04-04 2:11 ` Denys
2007-04-04 10:55 ` jamal
2007-04-04 12:56 ` Denys
2007-04-04 14:10 ` jamal
2007-04-04 14:35 ` Denys
2007-04-04 14:13 ` HTB/act_mirred problem [was: one more... iproute commands lockup whole system] Patrick McHardy
2007-04-04 14:33 ` jamal
2007-04-04 14:50 ` Patrick McHardy
2007-04-05 1:33 ` jamal
2007-04-04 13:36 ` one more... iproute commands lockup whole system Patrick McHardy
2007-04-04 13:58 ` jamal
2007-04-04 14:07 ` Patrick McHardy
2007-04-04 14:30 ` jamal
2007-04-04 14:39 ` Patrick McHardy
2007-04-05 2:14 ` jamal
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=20070322124533.M79867@visp.net.lb \
--to=denys@visp.net.lb \
--cc=kaber@trash.net \
--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.