Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: kasp <waters@inbox.lv>
To: lartc@vger.kernel.org
Subject: [LARTC] Slow large pings
Date: Sun, 09 Jan 2005 11:36:10 +0000	[thread overview]
Message-ID: <729574587.20050109133610@inbox.lv> (raw)

Hello lartc,

Testing some rules I found out that any rules are slowing down large pings!
For example:

tc qdisc add dev eth0 root handle 1: htb
tc class add dev eth0 parent 1: classid 1:1 htb rate 100Mbit prio 1 ceil 100Mbit
tc class add dev eth0 parent 1:1 classid 1:2 htb rate 100Mbit prio 2 ceil 100Mbit
tc filter add dev eth0 parent 1:0 prio 5 u32 \
    match ip src 10.10.10.1 \
    match ip dst 10.10.10.10 \
    flowid 1:2
tc qdisc add dev eth0 parent 1:2 handle 2: sfq perturb 10

Small pings are ok - <10ms, here is output for 65500 byte pings:

Pinging test [10.10.10.1] with 65500 bytes of data:

Reply from 10.10.10.1: bytese500 time\x120ms TTLd
Reply from 10.10.10.1: bytese500 time\x120ms TTLd
Reply from 10.10.10.1: bytese500 time\x120ms TTLd
Reply from 10.10.10.1: bytese500 time\x120ms TTLd

Ping statistics for 10.10.10.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 120ms, Maximum =  120ms, Average =  120ms

If I don't use any rules, 65500 byte pings are about ~10ms
Any filters are slowing large pings for 10 times!!!
What can I do to tune it up?

-- 
Best regards,
 kasp                          mailto:waters@inbox.lv

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2005-01-09 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 11:36 kasp [this message]
2005-01-13 13:05 ` [LARTC] Slow large pings Andy Furniss

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=729574587.20050109133610@inbox.lv \
    --to=waters@inbox.lv \
    --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