public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Ohlin <martin.ohlin@control.lth.se>
To: balbir@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: A nice CPU resource controller
Date: Wed, 30 Aug 2006 18:13:16 +0200	[thread overview]
Message-ID: <44F5B91C.1060209@control.lth.se> (raw)
In-Reply-To: <661de9470608300841o757a8704te4402a7015b230c5@mail.gmail.com>

Balbir Singh wrote:

> The CKRM e-series is a PID based CPU Controller. It did a good job of
> controlling and smoothing out the load (and variations) and even
> worked with groups. But it achieved all this through some amount of
> complexity. How do you plan to extend the idea to groups? Do you have
> any code that we can look at?

I would say that my controller so far is very simple, probably too 
simple. I have no detailed plan yet about how to incorporate groups of 
tasks, only small ideas that I would like to think a little more on 
before I say something embarrasing. The important code-parts are in the 
thesis, and I must say that the code is in no way finished, but most of 
it can be found at:
http://www.control.lth.se/user/martin.ohlin/linux/sampler.c

> I do not understand controlling the nice value? Most cpu control the
> bandwidth/time - are there any advantages to controlling the nice
> value? How does this interplay with dynamic priorities that the
> scheduler currently maintains?

There is a relationship between the nice value and the achieved 
bandwidth/time. Therefore it was possible that the nice value could be 
used to control the bandwidth/time. I wanted to know if it was possible 
to use it, and it was. As to the dynamic priorities, I do not change 
them, but as I do change the nice value and the dynamic priorities are 
relative to that, then you may say that I do change them... Anyway, it 
seems to work.

/Martin

  reply	other threads:[~2006-08-30 16:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30 15:14 A nice CPU resource controller Martin Ohlin
2006-08-30 15:41 ` Balbir Singh
2006-08-30 16:13   ` Martin Ohlin [this message]
2006-08-31  6:03     ` Balbir Singh
2006-08-31  1:07   ` Peter Williams
2006-08-31  6:17     ` Balbir Singh
2006-08-31 10:08       ` Peter Williams
2006-08-31 10:44       ` Mike Galbraith
2006-08-31  6:53     ` Mike Galbraith
2006-08-31  5:21       ` Peter Williams
2006-08-31  7:44         ` Mike Galbraith
2006-08-31  7:42       ` Mike Galbraith
2006-08-31 10:35         ` Martin Ohlin
2006-08-31 14:17           ` Mike Galbraith
2006-08-31 16:01           ` Chris Friesen
2006-08-31 19:14             ` Mike Galbraith
2006-08-31 23:52           ` Peter Williams
2006-08-31 10:21   ` Martin Ohlin
2006-08-31 11:13     ` Balbir Singh
2006-08-31 18:25 ` Peter Grandi

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=44F5B91C.1060209@control.lth.se \
    --to=martin.ohlin@control.lth.se \
    --cc=balbir@in.ibm.com \
    --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