LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: ck@vds.kolivas.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Con Kolivas <kernel@kolivas.org>
Subject: Re: Best CONFIG_HZ value for scheduler testing?
Date: Sun, 29 Apr 2007 16:07:23 +0200 (MEST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0704291606450.22744@yvahk01.tjqt.qr> (raw)
In-Reply-To: <200704271044.13916.Martin@lichtvoll.de>


On Apr 27 2007 10:44, 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...

CONFIG_HZ=1337
(SCNR.)


Jan
-- 

      parent reply	other threads:[~2007-04-29 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27  8:44 Martin Steigerwald
2007-04-28 19:29 ` Bill Davidsen
2007-04-29 14:07 ` Jan Engelhardt [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=Pine.LNX.4.61.0704291606450.22744@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=Martin@lichtvoll.de \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --subject='Re: Best CONFIG_HZ value for scheduler testing?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).