All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: ck@vds.kolivas.org, linux-kernel@vger.kernel.org
Subject: Re: Best CONFIG_HZ value for scheduler testing?
Date: Sat, 28 Apr 2007 15:29:45 -0400	[thread overview]
Message-ID: <4633A0A9.7090105@tmr.com> (raw)
In-Reply-To: <200704271044.13916.Martin@lichtvoll.de>

Martin Steigerwald wrote:
> Hi Con and Ingo!
> 
> What would be the best CONFIG_HZ value for scheduler testing? I used 
> 1000HZ for a long time, but use 300HZ since 2.6.20. This worked well 
> enough for sd-0.46 and previous versions and ck patches...
> 
That's a good point, all the tests I've done are at 1000, that's just my 
default and I didn't bother to change it.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  reply	other threads:[~2007-04-28 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27  8:44 Best CONFIG_HZ value for scheduler testing? Martin Steigerwald
2007-04-28 19:29 ` Bill Davidsen [this message]
2007-04-29 14:07 ` Jan Engelhardt

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=4633A0A9.7090105@tmr.com \
    --to=davidsen@tmr.com \
    --cc=Martin@lichtvoll.de \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@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.