From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: RES: [LARTC] Backlog with less rate than defined
Date: Tue, 25 Apr 2006 23:16:29 +0000 [thread overview]
Message-ID: <444EADCD.4050505@dsl.pipex.com> (raw)
In-Reply-To: <002001c6689d$49b439a0$0900fe0a@LucianoNotebook>
Luciano wrote:
> Hi Andy,
>
> I´m not sure if I understood what you told about arp packets.
> I use htb default but the problem occurs even when the default queue
> rate is low (it is almost always low in rate and pps).
It's still not ideal even if it's not the cause - sfq default length is
128 packets so if they were mtu size when it's full thats 1.5sec delay +
drops - and the stats show drops.
class htb 1:efff parent 1:1 leaf efff: prio 1 rate 1Mbit ceil 1Mbit
burst 2909b cburst 2909b
Sent 1113213839 bytes 9059857 pkts (dropped 61529, overlimits 0)
rate 1130bps 13pps
lended: 9059857 borrowed: 0 giants: 0
I would not use default on eth. Also 100mbit eth is not 100mbit at ip
level, which is almost what htb sees (ip+14), so 1:1 needs to be less -
but if children don't add up to that then it won't hurt.
You could just send all unmatched ip to 1:efff with a low prio filter -
tc filter add dev eth0 protocol ip parent 1:0 prio 99 u32 match u32 0 0
flowid 1:efff
then arp will not get shaped.
I notice you use handle on filters maybe OK but I usually only see it
with hashing or fw.
>
> The attached files are:
> Rc.local - criation of the basic queues including default
> Regras.inc - criation of each queue when the user login
> Queues - statistics of the basic queues
Have you measured the rate another way?
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-04-25 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 19:20 RES: [LARTC] Backlog with less rate than defined Luciano
2006-04-25 23:16 ` 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=444EADCD.4050505@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox