From: Andi Kleen <andi@firstfloor.org>
To: Hirofumi Nakagawa <hnakagawa@miraclelinux.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC][PATCH 0/1] MAZE: Mazed processes monitor
Date: Tue, 13 May 2008 23:07:52 +0200 [thread overview]
Message-ID: <87y76d7w0n.fsf@basil.nowhere.org> (raw)
In-Reply-To: <48297FD0.2090905@miraclelinux.com> (Hirofumi Nakagawa's message of "Tue, 13 May 2008 20:47:28 +0900")
Hirofumi Nakagawa <hnakagawa@miraclelinux.com> writes:
> This patch provides the mazed process monitor,named MAZE.
> MAZE's purpose is to notify or terminate registered processes when they are mazed.
> The definition of mazed process is a process using excessive CPU cycles,
> that is long time keeping TASK_RUNNING state.
Isn't that very similar to RLIMIT_CPU? The main difference seems to be
that they're regularly reset and that they can be more fine grained
than seconds.
How about you implement a way to change the RLIMIT_CPU limit
of a running task (and possibly fix it to use a finer grained unit
if you need <1s resolution).
Then you could run a user space daemon running with lower priority that
just regularly resets the RLIMIT_CPUs of all running processes.
If some RT process uses so much time that the user daemon cannot
keep up its cpu time limit will be eventually exceeded and it will
be killed.
I think that would be a far cleaner and generic way to implement
this.
-Andi
next prev parent reply other threads:[~2008-05-13 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 11:47 [RFC][PATCH 0/1] MAZE: Mazed processes monitor Hirofumi Nakagawa
2008-05-13 15:41 ` Andrew Morton
2008-05-22 9:31 ` Hirofumi Nakagawa
2008-05-13 21:07 ` Andi Kleen [this message]
2008-05-14 13:52 ` Hirofumi Nakagawa
2008-05-22 9:31 ` Hirofumi Nakagawa
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=87y76d7w0n.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=hnakagawa@miraclelinux.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