From: Nataniel Klug <nata@cnett.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QoS - Ping problem
Date: Thu, 06 Apr 2006 16:18:27 +0000 [thread overview]
Message-ID: <44353F53.6030401@cnett.com.br> (raw)
In-Reply-To: <44340CD6.1030907@cnett.com.br>
Jody,
I think I have founded the problem.
This interface uses a Realtek RTL8139D network pci card. I have made
many tests and I am thinking that this is the problem. When I sended all
traffic to another network card (3Com 905-TXM) it worked fine. I will
redo my concept about this hole thing.
Thanks for all answers I have get.
Att,
Nataniel Klug
Jody Shumaker escreveu:
>> CLASS="/sbin/tc class add dev $DL parent"
>> $CLASS 1: classid 1:1 htb rate 3072Kbit
>> $CLASS 1:1 classid 1:10 htb rate 1024Kbit ceil 1024Kbit
>> $CLASS 1:1 classid 1:20 htb rate 1536Kbit ceil 2560Kbit
>> $CLASS 1:1 classid 1:30 htb rate 512Kbit ceil 1024Kbit
>> $CLASS 1:1 classid 1:40 htb rate 512Kbit ceil 1024Kbit
>> $CLASS 1:1 classid 1:50 htb rate 512Kbit ceil 1024Kbit
>>
>>
>
> For starters you might want to fix these rates.
> 1024+1536+512+512+512 != 3072
>
> Over allocating may be causing the high number of dropped packets, and
> its at least worth fixing before trying anything else. Make sure child
> classes rates never add up to greater than the parents rate, in your
> case 3072Kbit. Beyond that though I don't see anything obvious. You're
> using sfq which what I usually see recommended to increase the queue
> size and avoid dropped packets.
>
> - Jody
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-04-06 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 18:30 [LARTC] QoS - Ping problem Nataniel Klug
2006-04-05 21:11 ` Jody Shumaker
2006-04-06 13:03 ` Nataniel Klug
2006-04-06 16:18 ` Nataniel Klug [this message]
2006-04-12 18:51 ` Andy Furniss
2006-04-12 19:26 ` Nataniel Klug
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=44353F53.6030401@cnett.com.br \
--to=nata@cnett.com.br \
--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.