From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB Rate and Prio (continued)
Date: Wed, 13 Jul 2005 22:15:28 +0000 [thread overview]
Message-ID: <42D59280.1030701@dsl.pipex.com> (raw)
In-Reply-To: <200507111126.j6BBQT5t007024@dhuumrelay0.mail.eu.uu.net>
Gael Mauleon wrote:
> Ok I tested the shaping on the SDSL line with netperf and
> an host outside.
>
> Same script than before, I classify the packets into qdisc based on the
> source address in netfilter and here are the result, that's with sfq.
> I'm positive on the right traffic going to the right class.
>
>
> TCP STREAM TEST to 81.57.243.113 (NORMAL)
> Recv Send Send
> Socket Socket Message Elapsed
> Size Size Size Time Throughput
> bytes bytes bytes secs. 10^3bits/sec
>
> 87380 8192 8192 60.00 282.90
>
>
>
> TCP STREAM TEST to 81.57.243.113 (LOWPRIO)
> Recv Send Send
> Socket Socket Message Elapsed
> Size Size Size Time Throughput
> bytes bytes bytes secs. 10^3bits/sec
>
> 87380 8192 8192 61.00 390.00
Hmm I can't really think why this is happening, is it the same box that
you did the lan test from?
I think what I would do as the next test is turn off window scaling -
echo 0 > /proc/sys/net/ipv4/tcp_window_scaling
add 70k bfifos to the classes - you shouldn't drop any packets then.
Repeat the test and tcpdump it. If you see packet loss then this could
be the explanation.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-07-13 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 11:27 [LARTC] HTB Rate and Prio (continued) Gael Mauleon
2005-07-11 18:44 ` Andy Furniss
2005-07-12 12:08 ` Gael Mauleon
2005-07-13 10:25 ` Gael Mauleon
2005-07-13 10:34 ` Gael Mauleon
2005-07-13 22:15 ` Andy Furniss [this message]
2005-07-13 22:26 ` Andy Furniss
2005-07-13 22:47 ` Andy Furniss
2005-07-15 8:24 ` Gael Mauleon
2005-07-15 10:26 ` Gael Mauleon
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=42D59280.1030701@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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 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.