From: Daniel Poelzleithner <poelzi@poelzi.org>
To: linux-kernel@vger.kernel.org
Subject: ANN: ulatencyd
Date: Sat, 08 Jan 2011 22:49:53 +0100 [thread overview]
Message-ID: <4D28DC01.2010901@poelzi.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Hi,
I'm proud to announce ulatencyd [1]. A scriptable daemon to dynamically
adjust Linux scheduling parameters and other things.
It is not ready for a release yet, but it works to a point I started to
get satisfied. I'm able to run a make -j 40 on my dual core machine
while looking a full hd movie without problems and the ui from kde still
feels good :-)
The architecture looks like this:
https://github.com/poelzi/ulatencyd/raw/master/docs/architecture.png
The rules usually only mark processes with flags that the scheduler uses
for his decision how to set the parameters of the process.
In special cases, the rule can enforce itself to schedule the process
itself, which is useful for reacting to attacks, for example.
There is still a lot of work to do. The scheduler itself was a quick
hack that needs a lot of work. There are currently no rules for swap of
death, fork-bombs, amok running processes,... and the scheduler has to
handle them of course.
There are already lots of optimization that minimize the amount of lua
code running, but the load on ulatencyd is high when a lot of processes
are spawned. This will be optimized soon.
[1] https://github.com/poelzi/ulatencyd/
PS: please CC if possible :-)
kind regards
Daniel Poelzleithner
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
reply other threads:[~2011-01-08 22:09 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=4D28DC01.2010901@poelzi.org \
--to=poelzi@poelzi.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