From: Con Kolivas <kernel@kolivas.org>
To: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Cc: Artur Skawina <art_k@o2.pl>,
linux list <linux-kernel@vger.kernel.org>,
ck list <ck@vds.kolivas.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sched: rsdl improvements
Date: Thu, 22 Mar 2007 11:24:58 +1100 [thread overview]
Message-ID: <200703221124.59126.kernel@kolivas.org> (raw)
In-Reply-To: <4601C44B.9060705@mnsu.edu>
On Thursday 22 March 2007 10:48, Jeffrey Hundstad wrote:
> Artur Skawina wrote:
> > Con Kolivas wrote:
> >> Note no interactive boost idea here.
> >>
> >> Patch is for 2.6.21-rc4-mm1. I have not spent the time trying to bring
> >> other bases in sync.
> >
> > I've tried RSDLv.31+this on 2.6.20.3 as i'm not tracking -mm.
> >
> >> Further improve the deterministic nature of the RSDL cpu scheduler and
> >> make the rr_interval tunable.
> >>
> >> By only giving out priority slots to tasks at the current runqueue's
> >> prio_level or below we can make the cpu allocation not altered by
> >> accounting issues across major_rotation periods. This makes the cpu
> >> allocation and latencies more deterministic, and decreases maximum
> >> latencies substantially. This change removes the possibility that tasks
> >> can get bursts of cpu activity which can favour towards interactive
> >> tasks but also favour towards cpu bound tasks which happen to wait on
> >> other activity (such as I/O) and is a net gain.
> >
> > I'm not sure this is going in the right direction... I'm writing
> > this while compiling a kernel w/ "nice -20 make -j2" and X is almost
>
> Did you mean "nice -20"? If so, that should have slowed X quite a bit.
> Try "nice 19" instead.
>
> nice(1):
> Run COMMAND with an adjusted niceness, which affects process
> scheduling. With no COMMAND, print the current niceness. Nicenesses
> range from -20 (most favorable scheduling) to 19 (least favorable).
No he's right. Something scrambled my brain and I've completely left out the
part where I offer the old bursts as a tunable option as well, which
unintentionally killed off SCHED_BATCH as an entity. I'll have to put that as
an additional patch sorry as this by itself is not always a win. Hang in
there.
--
-ck
next prev parent reply other threads:[~2007-03-22 0:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 17:29 [PATCH] sched: rsdl improvements Con Kolivas
2007-03-21 23:27 ` Artur Skawina
2007-03-21 23:48 ` Jeffrey Hundstad
2007-03-22 0:15 ` Artur Skawina
2007-03-22 0:24 ` Con Kolivas [this message]
2007-03-22 0:52 ` Con Kolivas
2007-03-22 2:04 ` [PATCH] sched: rsdl check for niced tasks lowering prio level Con Kolivas
2007-03-22 13:34 ` Artur Skawina
2007-03-21 23:36 ` [PATCH] sched: rsdl improvements Andrew Morton
2007-03-22 5:03 ` Con Kolivas
2007-03-22 14:46 ` Christian
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=200703221124.59126.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@linux-foundation.org \
--cc=art_k@o2.pl \
--cc=ck@vds.kolivas.org \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.