From: Al Boldi <a1426z@gawab.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org, Jake Moilanen <moilanen@austin.ibm.com>
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.3.1 for 2.6.16-rc5
Date: Wed, 5 Apr 2006 11:16:08 +0300 [thread overview]
Message-ID: <200604051116.08353.a1426z@gawab.com> (raw)
In-Reply-To: <4432FF26.6050207@bigpond.net.au>
Peter Williams wrote:
> Al Boldi wrote:
> > Peter Williams wrote:
> >> Al Boldi wrote:
> >>> The default values for spa make it really easy to lock up the system.
> >>> Is there a module to autotune these values according to cpu/mem/ctxt
> >>> performance?
> >>
> >> Jake Moilanen had a genetic algorithm autotuner for Zaphod at one time
> >> which I believe he ported over to PlugSched
> >
> > Would this be a load-adaptive dynamic tuner?
>
> Yes.
Wow!
> > What I meant was a lock-preventive static tuner. Something that would
> > take hw-latencies into account at boot and set values for non-locking
> > console operation.
>
> I'm not sure what you mean here. Can you elaborate?
In another thread Al Boldi wrote:
> After playing w/ these tunables it occurred to me that they are really
> only deadline limits, w/ a direct relation to cpu/mem/ctxt perf.
>
> i.e timeslice=1 on i386sx means something other than timeslice=1 on amd64
>
> It follows that w/o autotuning, the static default values have to be
> selected to allow for a large underlying perf range w/ a preference for
> the high range. This is also the reason why 2.6 feels really crummy on
> low perf ranges.
>
> Autotuning the default values would allow to tighten this range specific
> to the hw used, thus allowing for a smoother desktop experience.
> >> I could generate a patch to gather the statistic again and make them
> >> available via /proc if you would like to try a user space version of
> >> Jake's work (his was in kernel).
> >
> > That would be great!
>
> OK, I'll put it on my "to do" list.
Thanks!
--
Al
next prev parent reply other threads:[~2006-04-05 8:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 11:59 Al Boldi
2006-04-03 12:13 ` Paolo Ornati
2006-04-03 23:04 ` Peter Williams
2006-04-03 23:29 ` Con Kolivas
2006-04-04 0:01 ` Peter Williams
2006-04-04 0:12 ` Con Kolivas
2006-04-04 1:29 ` Peter Williams
2006-04-04 13:27 ` Al Boldi
2006-04-04 13:27 ` Al Boldi
2006-04-04 23:17 ` Peter Williams
2006-04-05 8:16 ` Al Boldi
2006-04-05 22:53 ` Peter Williams
2006-04-07 21:32 ` Al Boldi
2006-04-08 1:29 ` Peter Williams
2006-04-08 20:31 ` Al Boldi
2006-04-09 2:58 ` Peter Williams
2006-04-09 5:04 ` Al Boldi
2006-04-09 23:53 ` Peter Williams
2006-04-10 14:43 ` Al Boldi
2006-04-11 2:07 ` Peter Williams
2006-04-03 23:27 ` Peter Williams
2006-04-04 13:27 ` Al Boldi
2006-04-04 23:20 ` Peter Williams
2006-04-05 8:16 ` Al Boldi [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 22:32 Peter Williams
2006-03-01 2:36 ` Peter Williams
2006-04-02 2:04 ` Peter Williams
2006-04-02 6:02 ` Con Kolivas
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=200604051116.08353.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moilanen@austin.ibm.com \
--cc=pwil3058@bigpond.net.au \
/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
all inboxes | Powered by JetHome®