From: Con Kolivas <kernel@kolivas.org>
To: ck@vds.kolivas.org
Cc: Al Boldi <a1426z@gawab.com>, linux-kernel@vger.kernel.org
Subject: Re: [ck] Re: [PATCH] [RSDL-0.30] sched: rsdl improve latencies with differential nice -1
Date: Wed, 14 Mar 2007 07:27:37 +1100 [thread overview]
Message-ID: <200703140727.37486.kernel@kolivas.org> (raw)
In-Reply-To: <200703132254.28281.a1426z@gawab.com>
On Wednesday 14 March 2007 06:54, Al Boldi wrote:
> Con Kolivas wrote:
> > On Wednesday 14 March 2007 03:03, Con Kolivas wrote:
> > > On Wednesday 14 March 2007 02:31, Con Kolivas wrote:
> > > > On Monday 12 March 2007 22:26, Al Boldi wrote:
> > > > > I think, it should be possible to spread this max expiration
> > > > > latency across the rotation, should it not?
> > > >
> > > > Can you try the attached patch please Al and Mike? It "dithers" the
> > > > priority bitmap which tends to fluctuate the latency a lot more but
> > > > in a cyclical fashion. This tends to make the max latency bound to a
> > > > smaller value and should make it possible to run -nice tasks without
> > > > killing the latency of the non niced tasks. Eg you could possibly run
> > > > X nice -10 at a guess like we used to in 2.4 days. It's not essential
> > > > of course, but is a workaround for Mike's testcase.
> > >
> > > Oops, one tiny fix. This is a respin of the patch, sorry.
> >
> > A few other minor things would need to be updated before this patch is in
> > a good enough shape to join the rsdl patches. This one will be good for
> > testing though.
>
> Applied against v0.30 mainline. It only works on prio +16 to +19.
I guess the "other minor things" will matter then :) I'll keep working. At
least you know what I'm working on now.
--
-ck
prev parent reply other threads:[~2007-03-13 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 19:54 [PATCH] [RSDL-0.30] sched: rsdl improve latencies with differential nice -1 Al Boldi
2007-03-13 20:27 ` Con Kolivas [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=200703140727.37486.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=a1426z@gawab.com \
--cc=ck@vds.kolivas.org \
--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