From: Timothy Miller <miller@techsource.com>
To: Kurt Garloff <garloff@suse.de>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: dynamic sched timeslices
Date: Tue, 16 Mar 2004 10:03:39 -0500 [thread overview]
Message-ID: <4057174B.3050305@techsource.com> (raw)
In-Reply-To: <20040315224201.GX4452@tpkurt.garloff.de>
Kurt Garloff wrote:
> Hi,
>
> attached patch allows userspace to tune the scheduling timeslices.
> It can be used for a couple of things:
> * Tune a workload for batch processing:
> You'd probably wnat to use long timeslices in order to not reschedule
> as often to make good use of your CPU caches
> * Tune a workload for interactive use:
> Under load, you may want to reduce the scedulilng latencies by using
> shorter timeslices (and there are situations where the interactiviy
> tweak -- even if they were perfect -- can't save you).
> * Tune the ration betweeen maximum and minimum timeslices to make
> nice much nicer e.g.
>
> The patch exports /proc/sys/kernel/max_timeslice and min_timeslice,
> unites are us. It also exports HZ (readonly).
> The patch implementes the desktop boot parameter which introduces
> shorter timeslices.
>
> Patch is from andrea and is in our 2.4 tree; 2.6 port was done by me and
> straightforward.
>
> Regards,
If this doesn't change the total amount of CPU a process can get but
lets a process tweak how its CPU time is divided up, then it sounds
wonderful.
next prev parent reply other threads:[~2004-03-16 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 22:42 dynamic sched timeslices Kurt Garloff
2004-03-15 22:59 ` Christoph Hellwig
2004-03-15 23:09 ` Kurt Garloff
2004-03-15 23:40 ` Andrew Morton
2004-03-16 11:36 ` Kurt Garloff
2004-03-16 13:13 ` Con Kolivas
2004-03-16 14:29 ` Kurt Garloff
2004-03-16 20:45 ` Con Kolivas
2004-03-18 0:20 ` Kurt Garloff
2004-03-18 0:32 ` Andrew Morton
2004-03-18 3:38 ` Con Kolivas
2004-03-16 15:03 ` Timothy Miller [this message]
2004-03-16 15:08 ` Kurt Garloff
2004-03-23 9:23 ` Pavel Machek
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=4057174B.3050305@techsource.com \
--to=miller@techsource.com \
--cc=garloff@suse.de \
--cc=linux-kernel@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