Re: [LARTC] filter ingress policy rates -> slow!!

[gypsy <gypsy@iswest.com>]

"Edulix (by way of Edulix )" wrote:
> Anyway, here you can all see the problem:
> 
> # tc -s -d qdisc
> qdisc ingress ffff: dev eth0 ----------------
>  Sent 5109350 bytes 13696 pkts (dropped 935, overlimits 0)
> 
> And the only tc rules I executed were:
> 
> tc qdisc add dev eth0 handle ffff: ingress
> tc filter add dev eth0 parent ffff: protocol ip prio 10 u32 \
>         match ip src 192.168..0.0/24 \
>         match ip dst 192.168..0.0/24 \
>         police rate 100mbit burst 10k drop flowid :2
> 
> In this test I did is just overing the kde's taskbar and clicking in the K
> menu. BTW, I'll tell you that many operations work fine, but there'are some
> (as the one's Ive just refered to) that are rather slow.
> 
> Now, let's see what is the maximun ssh speed:
> # scp
> edulix@192.168.0.7:/home/edulix/videos/prodigy90_med.mpg /home/edulix/temp/
> prodigy90_med.mpg                                     11%  992KB  45.0KB/s
> 
> Mamma mia! That must demostrate the problem hehe. In normal conditions that
> video is transfered in less than 3 seconds at 7-8 Mb/s! After doing that, I
> can see:
> # tc -s -d qdisc
> qdisc ingress ffff: dev eth0 ----------------
>  Sent 30133742 bytes 88401 pkts (dropped 4792, overlimits 0)
> 
> Cheers,
>           Edulix.

Did you build your own kernel?  If not, do.  If so:
1) What kernel version?
2) Post results of
grep "define PSCHED_CLOCK" /usr/src/linux/incluce/net/pkt_sched.h

Google "LARTC accuracy" and whatever else you can find from this list
regarding having to set the rate based on results rather than what you
know the rate to be.

Keep Steph involved; he's The Master.
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/