public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org,
	Mike Galbraith <efault@gmx.de>
Subject: Re: [RFC] sched.c : procfs tunables
Date: Mon, 3 Apr 2006 22:21:31 +1000	[thread overview]
Message-ID: <200604032221.32461.kernel@kolivas.org> (raw)
In-Reply-To: <200604031459.43105.a1426z@gawab.com>

On Monday 03 April 2006 21:59, Al Boldi wrote:
> Con Kolivas wrote:
> > None of the current "tunables" have easily understandable heuristics.
> > Even those that appear to be obvious, like timselice, are not. While
> > exporting tunables is not a bad idea, exporting tunables that noone
> > understands is not really helpful.
>
> Couldn't this be fixed with an autotuning module based on cpu/mem/ctxt
> performance?

You're assuming there is some meaningful relationship between changes in 
cpu/mem/ctxt performance and these tunables, which isn't the case. 
Furthermore if this was the case, noone understands it, can predict it or 
know how to tune it. Just saying "autotune it" doesn't really tell us how 
exactly the change those tunables in relation to the other variables. Since 
Mike and I understand them reasonably well I think we'd both agree that there 
is no meaningful association.

Cheers,
Con

  reply	other threads:[~2006-04-03 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 14:23 [RFC] sched.c : procfs tunables Al Boldi
2006-03-31 14:44 ` Con Kolivas
2006-04-03 11:59   ` Al Boldi
2006-04-03 12:21     ` Con Kolivas [this message]
2006-04-04 13:27       ` Al Boldi
2006-04-07  2:47         ` Bill Davidsen
2006-04-03 12:43     ` Mike Galbraith
2006-04-01  2:49 ` Mike Galbraith
2006-04-07  2:57 ` Bill Davidsen

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=200604032221.32461.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=a1426z@gawab.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-smp@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