From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] random ia64 sched-domains values
Date: Sat, 26 Feb 2005 00:25:16 +0000 [thread overview]
Message-ID: <200502260025.j1Q0PGg10838@unix-os.sc.intel.com> (raw)
In-Reply-To: <421EDE70.3010501@yahoo.com.au>
Nick Piggin wrote on Friday, February 25, 2005 3:42 PM
> >>These are some values I just found from thin-air that should
> >>hopefully make ia64 work after the latest sched patches.
> >>
> >>+ .cache_hot_time = (10*1000000), \
> >
> >
> > In 2.6.9, cache_hot_time gets the value from cache_decay_tick, since
> > when this become a constant again?
> >
>
> Not sure. cache_decay_ticks isn't set to anything meaningful on
> ia64 anyway. Nor i386 for that matter.
This parameter is known to be sensitive for one db workload. It was
discussed about 4 month back. The conclusion was that there is NO one
magic constant that works for every workloads on every platforms. Until
a new auto tune algorithm is written/tested, it was decided that we use
cache_decay_ticks as a boot time tunable for cache_hot_time.
I guess it somehow got lost soon after 2.6.9. This needs to be reinstated.
Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
--- linux-2.6.10/include/linux/topology.h Fri Jan 7 21:44:04 2005
+++ linux-2.6.10/include/linux/topology.h Fri Feb 25 16:02:44 2005
@@ -109,7 +109,7 @@
.max_interval = 4, \
.busy_factor = 64, \
.imbalance_pct = 125, \
- .cache_hot_time = (5*1000000/2), \
+ .cache_hot_time = cache_decay_ticks*1000000 ? : (5*1000000/2),\
.cache_nice_tries = 1, \
.per_cpu_gain = 100, \
.flags = SD_LOAD_BALANCE \
next prev parent reply other threads:[~2005-02-26 0:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 8:14 [PATCH] random ia64 sched-domains values Nick Piggin
2005-02-25 18:46 ` Chen, Kenneth W
2005-02-25 23:41 ` Nick Piggin
2005-02-26 0:25 ` Chen, Kenneth W [this message]
2005-02-26 0:40 ` Chen, Kenneth W
2005-02-26 0:48 ` Nick Piggin
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=200502260025.j1Q0PGg10838@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox