From: Artur Skawina <skawina@geocities.com>
To: Kurt Garloff <garloff@suse.de>
Cc: linux-kernel@vger.rutgers.edu,
Harald Koerfgen <Harald.Koerfgen@home.ivm.de>
Subject: Re: [RFC] increasing and masquerading HZ
Date: Tue, 20 Jul 1999 13:21:31 +0200 [thread overview]
Message-ID: <37945BBB.711FAFA5@geocities.com> (raw)
In-Reply-To: 19990720105551.C9486@bari.suse.de
Kurt Garloff wrote:
>
> Without looking into details, I saw a place, where I did HZ conversion where
i did that conversion after doing the math, to avoid doing it twice, iirc.
> You may want to merge your patch with one from
> Harald Koerfgen <Harald.Koerfgen@home.ivm.de>
> on
> ftp://ftp.linux.sgi.com/pub/linux/mips/test/hz_patch.gz
>
> He mailed me about necessary changes for his MIPS work. I did not yet find
> time to answer him, but maybe you can contact him and get the changes merged.
except the mips-only change, the only thing missing is one #include "param.h".
> Basically, independance of userspace from the internal HZ is good. This is
yes, it's a requirement. There are still a few issues left:
o stability - the machine i tried this on locked up hard while running
a kernel with this patch. It's otherwise rock solid... Hmm, was there
a known (scheduling) bug in 2.3.5 that could get triggered by a big HZ?
Will try to reproduce...
o the ip routing sysctls (i'd rather not touch these)
o /proc/net/tcp and friends (look at the "netstat -to" output...),
this one will be easy to fix.
artur
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~1999-07-20 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-20 3:32 [RFC] increasing and masquerading HZ Artur Skawina
1999-07-20 8:55 ` Kurt Garloff
1999-07-20 11:21 ` Artur Skawina [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=37945BBB.711FAFA5@geocities.com \
--to=skawina@geocities.com \
--cc=Harald.Koerfgen@home.ivm.de \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.rutgers.edu \
/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.