From: Hirofumi Nakagawa <hnakagawa@miraclelinux.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org
Subject: [RFC][PATCH 0/1] MAZE: Mazed processes monitor
Date: Tue, 13 May 2008 20:47:28 +0900 [thread overview]
Message-ID: <48297FD0.2090905@miraclelinux.com> (raw)
Hi all.
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.
MAZE detects mazed processes and sends specified signals to them.
This implements a CGL (Carrier Grade Linux) requirement (AVL.14.0).
Possible uses:
* High-Availability system
* system using many Real-Time processes such as embedded
Please any comments!
Hirofumi Nakagawa
--- Usage
Add monitoring process.
% echo "1234 10000 20000 24 9" > /proc/maze/entries
The numeric values are "pid","soft limit [msec]","hard limit [msec]",
"soft signal" and "hard signal".
Get monitoring process list.
% cat /proc/maze/entries
--- Example
As follows example express the feature of MAZE function.
--
#include <sys/types.h>
#include <sys/wait.h>
#include <unistd.h>
#include <stdio.h>
#include <stdlib.h>
int main(int argc, char *argv[])
{
int state,i;
char cmd[128];
sprintf(cmd, "echo \"%d 10000 20000 24 9\" > /proc/maze/entries", getpid());
system(cmd);
if (!fork()) {
printf("Mazed process start.\n");
for(;;);
}
if (!fork()) {
printf("Not mazed process start.\n");
for(i = 0;i < 20; i++)
sleep(1);
printf("Not mazed process finish.\n");
exit(0);
}
for (i = 0;i < 2; i++)
wait(&state);
return 0;
}
--
---
next reply other threads:[~2008-05-13 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 11:47 Hirofumi Nakagawa [this message]
2008-05-13 15:41 ` [RFC][PATCH 0/1] MAZE: Mazed processes monitor Andrew Morton
2008-05-22 9:31 ` Hirofumi Nakagawa
2008-05-13 21:07 ` Andi Kleen
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=48297FD0.2090905@miraclelinux.com \
--to=hnakagawa@miraclelinux.com \
--cc=akpm@linux-foundation.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 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.