All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jack F. Vogel" <jfv@trane.bluesong.net>
To: m.knoblauch@TeraPort.de
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	jfv@us.ibm.com
Subject: Re: [PATCH]: O(1) 2.4.17-J7 Tuneable Parameters
Date: Wed, 30 Jan 2002 17:44:18 -0800	[thread overview]
Message-ID: <200201310144.g0V1iJs26742@Bluesong.NET> (raw)
In-Reply-To: <3C57F347.26527F73@TeraPort.de>
In-Reply-To: <3C57F347.26527F73@TeraPort.de>

On Wednesday 30 January 2002 05:21 am, Martin Knoblauch wrote:
> > [PATCH]: O(1) 2.4.17-J7 Tuneable Parameters
>
>
>  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?

Running on a machine that I dont think I can really officially give numbers..
However, lets say that without the tuneable code you got a run of hackbench
doing 60 groups that took 8.27 secs, when the tuneable code is in it went
to a whopping 8.6 secs :)

The results at least on this benchmark were all in that decimal noise.

As for a build option, if the code were integrated I might see that as 
making sense, but as this is a developmental patch the user is expected
to know what they are doing. Only root can write anything to the parameters
as well.

Cheers,

-- 
Jack F. Vogel
IBM  Linux Solutions
jfv@us.ibm.com  (work)
jfv@Bluesong.NET (home)

  parent reply	other threads:[~2002-01-31  1:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 13:21 [PATCH]: O(1) 2.4.17-J7 Tuneable Parameters Martin Knoblauch
2002-01-30 21:05 ` Rob Landley
2002-01-31  1:44 ` Jack F. Vogel [this message]
  -- 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=200201310144.g0V1iJs26742@Bluesong.NET \
    --to=jfv@trane.bluesong.net \
    --cc=jfv@bluesong.net \
    --cc=jfv@us.ibm.com \
    --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 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.