From: Michele Petrazzo - Unipex <michele.petrazzo@unipex.it>
To: Lucas Willian Bocchi <challado@ampernet.com.br>
Cc: netfilter@vger.kernel.org
Subject: Re: Best Kernel QoS Parameters
Date: Fri, 16 Oct 2009 13:28:52 +0200 [thread overview]
Message-ID: <4AD858F4.4050709@unipex.it> (raw)
In-Reply-To: <4AD48D3F.6000502@ampernet.com.br>
Lucas Willian Bocchi wrote:
> Hello all!
>
Hi,
> My question is simple: to a linux router, how are the kernel
> parameters (2.6 kernel tree) to set to make a good and responsive
> kernel to best QoS Shaping (HTB, HFSC, etc)?
>
From my point of view, into a normal environment, the last problem is
which packet scheduler choose. All those are so well builds that when
your setup don't work like you want, the right question must be "where
I'm wrong?" and not "can be the shaper wrong or there is a bug inside?"
For me, for a newbie, the right one are htb. Simple and with a good
documentation / cookbook.
> Another question is: how are the effect of TX and RX Ring Buffer
> (hardware packet buffer) in QoS? The algoritms use these parameters
> in the QoS configuration? I presume that this parameters can affect
> the performance, because the hardware buffer can borrow the QoS
> configuration.
I haven't read the sources and I'm not a kernel devel, so I don't know
exactly how are the hw buffer use, but I can ensure you that I tried
more than one type of ethernet cards into a heavy use systems (google
for ml archives) and a good card it's one of the best buys that you can do
Michele
next prev parent reply other threads:[~2009-10-16 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 14:22 Best Kernel QoS Parameters Lucas Willian Bocchi
2009-10-16 11:28 ` Michele Petrazzo - Unipex [this message]
[not found] ` <4AD86551.4050201@ampernet.com.br>
2009-10-16 13:04 ` Michele Petrazzo - Unipex
2009-10-16 13:25 ` Lucas Willian Bocchi
2009-10-23 13:53 ` Michele Petrazzo - Unipex
-- strict thread matches above, loose matches on Subject: below --
2009-10-16 13:10 Lucas Willian Bocchi
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=4AD858F4.4050709@unipex.it \
--to=michele.petrazzo@unipex.it \
--cc=challado@ampernet.com.br \
--cc=netfilter@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