From: Michael Renzmann <lartc@nospam.otaku42.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] netem bug?
Date: Thu, 27 Jan 2005 15:09:30 +0000 [thread overview]
Message-ID: <41F9042A.9090400@otaku42.de> (raw)
In-Reply-To: <41F8F6FD.6040408@poli.usp.br>
Hi.
Catalin(ux aka Dino) BOIE wrote:
> The "problem" is the 2.4 kernel because HZ is 100.
That was my idea, too.
> On my 2.6 kernel (HZ\x1000) it work almost perfect.
If the OP thinks of changing HZ, the following links might be a good help:
http://www.plumlocosoft.com/kernel/
(especially 013-j64.diff.bz2 and 014-vhz.diff.bz2)
http://kerneltrap.org/node/464/1528
The mentioned patches allow to change HZ to something else than 100
while retaining compatibility to userspace and other stuff that might
rely on HZ being 100. Note that kernel image as well as (most probably
all) modules have to be recompiled and replaced for the patch to take
effect.
Bye, Mike
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-01-27 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 14:13 [LARTC] netem bug? Pedro Ancona Lopez Mindlin
2005-01-27 14:42 ` Catalin(ux aka Dino) BOIE
2005-01-27 15:09 ` Michael Renzmann [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=41F9042A.9090400@otaku42.de \
--to=lartc@nospam.otaku42.de \
--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.