From: Bill Davidsen <davidsen@tmr.com>
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: Thu, 06 Apr 2006 22:57:40 -0400 [thread overview]
Message-ID: <4435D524.6020403@tmr.com> (raw)
In-Reply-To: <200603311723.49049.a1426z@gawab.com>
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.
>
>
I'm not sure I would agree about distribution kernels, and kernel.org
kernels certainly have the options to trade overhead for more response.
>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?
>
>
Let me agree with Mike and Con, I understand just well enough to pretty
much leave them alone. The swappiness is available, that's one of the
things which wants tuning. But the old 2.2 kernels did run better on
small machines, even a stripped 2.6 kernel is slower.
>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
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-smp" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2006-04-07 2:57 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
2006-04-07 2:57 ` Bill Davidsen [this message]
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=4435D524.6020403@tmr.com \
--to=davidsen@tmr.com \
--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 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).