From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] About HTB3
Date: Sun, 23 Jun 2002 09:39:59 +0000 [thread overview]
Message-ID: <marc-lartc-102482523709959@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102454870301498@msgid-missing>
On Thu, Jun 20, 2002 at 10:45:11AM +0500, Alexey Talikov wrote:
> Don't set HZ to 1024 on intel - it a bad idea
> it produce many problem for other parts of linux which use HZ\x100
Can you elaborate? I know of only the 'top' problem but most other things
work well.
If you raise HZ you will get more precise shaping and less bursty traffic.
Regards,
bert
--
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/
next prev parent reply other threads:[~2002-06-23 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 4:53 [LARTC] About HTB3 yangrunhua
2002-06-20 5:45 ` Alexey Talikov
2002-06-23 9:39 ` bert hubert [this message]
2002-06-24 4:34 ` Alexey Talikov
2002-06-24 7:29 ` Martin Devera
2002-06-24 7:40 ` Amit Kucheria
2002-06-24 7:52 ` Martin Devera
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-102482523709959@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox