From: Edulix <edulix@tumundoweb.com>(by way of Edulix <edulix@tumundoweb.com>)
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filter ingress policy rates -> slow!!
Date: Fri, 02 Jul 2004 08:36:28 +0000 [thread overview]
Message-ID: <200407021036.28648.edulix@tumundoweb.com> (raw)
In-Reply-To: <200407011810.01786.edulix@tumundoweb.com>
El Viernes, 2 de Julio de 2004 03:46, gypsy escribió:
> Edulix wrote:
> > (That command starts *only* ingress policies)
> > [root@k12ltsp-server root]# tc -s -d qdisc
> > qdisc ingress ffff: dev eth0 ----------------
> > Sent 384 bytes 3 pkts (dropped 0, overlimits 0)
> > [root@k12ltsp-server root]#
>
> This is a joke? You have not demonstrated any slowdown.
Sorry, I didn't undertand very well the thing :-P. Also, I haven't got
permanent access to other's pc of the network (they're not mine
;-)!) and that's the reason because I posted the counters as is.
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/
Warning: Permanently added '192.168.0.7' (RSA) to the list of known hosts.
edulix@192.168.0.7's password:
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.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-07-02 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 16:10 [LARTC] filter ingress policy rates -> slow!! Edulix
2004-07-01 20:40 ` Stef Coene
2004-07-02 8:36 ` Edulix [this message]
2004-07-02 14:13 ` gypsy
2004-07-03 4:14 ` gypsy
2004-07-03 9:44 ` Edulix
2004-07-03 11:09 ` Ed Wildgoose
2004-07-03 11:47 ` Edulix
2004-07-03 13:13 ` Ed Wildgoose
2004-07-03 15:02 ` gypsy
2004-07-03 22:25 ` Edulix
2004-07-04 19:47 ` gypsy
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=200407021036.28648.edulix@tumundoweb.com \
--to=edulix@tumundoweb.com \
--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