From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TBF to limit bandwidth, Should I change #define HZ?
Date: Sat, 31 Aug 2002 11:28:27 +0000 [thread overview]
Message-ID: <marc-lartc-103079338506733@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103074075811159@msgid-missing>
On Fri, Aug 30, 2002 at 06:00:37PM -0300, Fernando Lemos de Mello wrote:
> Dear friends,
>
> thanks for the last advices about TBF.
>
> After reading the tbf.pdf document I got a better insight of the problems I
> had trying to limit the bandwith on my testbed with a high resolution.
>
> The question I have now is:
> Would I get an immediatly better resolution result if I change the #define
> HZ to 1000 for my Linux box? I have a Pentium Celeron 700 MHz, and I would
> like to see the tbf working like:
You don't need to change HZ, for most purposes, it suffices to just raise
the burst size, which means 'send some packets' 'wait 10 ms' 'send some more
packets'. This will even out just fine.
> So if I change the file /usr/src/linux/include/asm-i386/param.h: #define HZ
> 100 to #define HZ 1000 and simply recompile the kernel, would tc work with
> better resolution?
Yes.
Kind regards,
bert hubert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-08-31 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 20:52 [LARTC] TBF to limit bandwidth, Should I change #define HZ? Fernando Lemos de Mello
2002-08-31 11:28 ` bert hubert [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=marc-lartc-103079338506733@msgid-missing \
--to=ahu@ds9a.nl \
--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.