From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: jfv@trane.bluesong.net
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: O(1) 2.4.17-J7 Tuneable Parameters
Date: Wed, 30 Jan 2002 14:21:11 +0100 [thread overview]
Message-ID: <3C57F347.26527F73@TeraPort.de> (raw)
> [PATCH]: O(1) 2.4.17-J7 Tuneable Parameters
>
>
> Hi Ingo,
>
> This patch synchronizes with J7 and I think makes the changes
> you wished. A couple of important points:
>
> - This patch can be applied to EITHER 2.4.17 OR 2.4.18 pre 7 as
> long as Ingo's J7 patch is applied first.
>
> - While I agree with you on not wanting these in the mainline kernel,
> I ran Hackbench on one of our new Foster systems with and
> without the tuneable parameters, and while the numbers do
> degrade slightly, its rather suprisingly small. So dont be afraid
> to use this as a system tuning aid.
>
How big is the actual degradation in your test? IIR, Ingo is afraid
that the tunables could easily screw things up, which of course is true.
What about adding a kernel-build option that leaves the sysctl interface
read-only by default and enables writing only if it is requested at
build time?
That way the external interface stays constant.
Martin
--
------------------------------------------------------------------
Martin Knoblauch | email: Martin.Knoblauch@TeraPort.de
TeraPort GmbH | Phone: +49-89-510857-309
C+ITS | Fax: +49-89-510857-111
http://www.teraport.de | Mobile: +49-170-4904759
next reply other threads:[~2002-01-30 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 13:21 Martin Knoblauch [this message]
2002-01-30 21:05 ` [PATCH]: O(1) 2.4.17-J7 Tuneable Parameters Rob Landley
2002-01-31 1:44 ` Jack F. Vogel
-- strict thread matches above, loose matches on Subject: below --
2002-01-26 7:12 Jack F. Vogel
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=3C57F347.26527F73@TeraPort.de \
--to=martin.knoblauch@teraport.de \
--cc=jfv@trane.bluesong.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.knoblauch@TeraPort.de \
/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