From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Cc: linux-smp@vger.kernel.org
Subject: [RFC] sched.c : procfs tunables
Date: Fri, 31 Mar 2006 17:23:49 +0300 [thread overview]
Message-ID: <200603311723.49049.a1426z@gawab.com> (raw)
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?
All comments that have a vested interest in enabling Linux on the desktop are
most welcome, even if they describe other/better/smarter approaches.
Thanks!
--
Al
next reply other threads:[~2006-03-31 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 14:23 Al Boldi [this message]
2006-03-31 14:44 ` [RFC] sched.c : procfs tunables 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
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=200603311723.49049.a1426z@gawab.com \
--to=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 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 read-only IMAP folder(s) and NNTP newsgroup(s).