From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Question: traffic shaping (tc-htb)
Date: Mon, 30 May 2005 20:44:02 +0000 [thread overview]
Message-ID: <429B7B12.8090302@dsl.pipex.com> (raw)
In-Reply-To: <002d01c56525$5d124180$0b00000a@jo>
John Smith wrote:
> Hello *!
> My trafficshaping (tc-htb) drops packets very early, at least i suspect
> this. It drops about 30% fo the packets. The traffic-generating appication
> is running locally on the shaping host. I think i can lower this rate by
> increasing the packet-buffer, because the locally application will slow down
> with increasing buffer (tcp/ip). But i can´t find any options for that, i
> cycled the manual several times. Is there a solution?
>
>
>
>
> see output of "tc -s -d class show dev ppp0" (main class):
> class htb 1:10 parent 1:1 prio 1 quantum 1800 rate 144000bit
> ceil 480000bit burst 1779b/8 mpu 0b overhead 0b cburst 2199b/8
> mpu 0b overhead 0b level 0
> Sent 57567157 bytes 40609 pkts (dropped 16033, overlimits 0)
> rate 460328bit 40pps
> lended: 12845 borrowed: 27764 giants: 0
> tokens: -74623 ctokens: -28826
>
> This class is the only one with packet drops. Does tc use the kernels
> network packet queue?
HTB uses the txqueuelength of the interface if you don't add a queue to
the leaf class. For my ppp0 that's 3 which is a bit short - even so I
just did a test and only got 10% loss so maybe your generator app/kernel
version of tcp is a bit over aggressive. I did 1 tcp stream with netperf
on 2.6.12-rc1.
So either add a queue to the leaf and specify a length or before you
start htb do ifconfig ppp0 txqueuelen 30 or whatever.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-05-30 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 14:39 [LARTC] Question: traffic shaping (tc-htb) John Smith
2005-05-30 20:44 ` Andy Furniss [this message]
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=429B7B12.8090302@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.