From: Mike Galbraith <efault@gmx.de>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: [RFC] sched.c : procfs tunables
Date: Sat, 01 Apr 2006 04:49:39 +0200 [thread overview]
Message-ID: <1143859779.7762.56.camel@homer> (raw)
In-Reply-To: <200603311723.49049.a1426z@gawab.com>
On Fri, 2006-03-31 at 17:23 +0300, Al Boldi wrote:
> Proper scheduling in a multi-tasking environment is critical to the success
> of a desktop OS. Linux, being mainly a server OS, is currently tuned to
> scheduling defaults that may be appropriate only for the server scenario.
>
> To enable Linux to play an effective role on the desktop, a more flexible
> approach is necessary. An approach that would allow the end-User the
> freedom to adjust the OS to the specific environment at hand.
>
> So instead of forcing a one-size fits all approach on the end-User, would not
> exporting sched.c tunables to the procfs present a flexible approach to the
> scheduling dilemma?
Nope, not the existing tunables anyway. The full effect of even a tiny
scheduler knob tweak is hard to predict even if you've studied the code
carefully. These knobs are just not generic enough to be exposed IMHO.
-Mike
next prev parent reply other threads:[~2006-04-01 2:49 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
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 [this message]
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=1143859779.7762.56.camel@homer \
--to=efault@gmx.de \
--cc=a1426z@gawab.com \
--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 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.