From: Martin Andersson <martin.andersson@control.lth.se>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: [RFC][PATCH 5/9] CPU controller - Documents how the controller works
Date: Mon, 24 Apr 2006 11:23:41 +0200 [thread overview]
Message-ID: <444C991D.4010804@control.lth.se> (raw)
> A better way to achieve the desired group cpu usage IMHO would be to
> adjust nice level of members at slice refresh time. This way, you get
> the timeslice scaling and priority adjustment all in one.
>
> (I think I would do both actually, with nice level being preferred such
> that dynamic priority spread within the group isn't flattened, which can
> cause terminal starvation within the group, unless really required.)
I am actually working on something more or less like that as part of my
licentiate (half time PhD) thesis. In the thesis I want to control CPU
resources using a control theoretic approach. The results so far are
very promising, but my code is not very mature yet. I plan to have my
thesis ready during this summer, so if anyone is interested I can mail
you a copy. If I have the time after that, I will try to incorporate my
code into the CKRM framework.
/Martin Andersson
reply other threads:[~2006-04-24 9:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=444C991D.4010804@control.lth.se \
--to=martin.andersson@control.lth.se \
--cc=efault@gmx.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 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.