From: Hirofumi Nakagawa <hnakagawa@miraclelinux.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, Andi Kleen <andi@firstfloor.org>
Subject: [RFC][PATCH 0/2 v2] MAZE: Introduction
Date: Thu, 22 May 2008 19:01:13 +0900 [thread overview]
Message-ID: <48354469.40100@miraclelinux.com> (raw)
Hi all,
MAZE provides a mechanism for detecting excessive CPU cycle usage of
selected processes and sending signals to them.
The definition of excessive CPU cycle usage is staying in TASK_RUNNINT
state for a long time.
Normally, a working process doesn't stay long time in TASK_RUNNING state
because of occasional IO waits or calling sleeps.
MAZE detects excessive CPU cycle usage from process's information and sends
signal when time of staying in TASK_RUNNING exceeds user defined limits.
The aim is to implement a CGL (Carrier Grade Linux) requirement (AVL.14.0).
Quote from CGL specification: (http://developer.osdl.org/dev/cgl/cgl40/cgl40-availability.pdf)
OSDL CGL specifies that carrier grade Linux shall provide a
mechanism that detects excessive CPU cycle usage by any process or thread.
To enable detection, the following capabilities shall be provided:
- Communication between the monitoring process and the kernel.
- Registering a list of processes or threads and their allowed CPU cycle
thresholds.
- Ability to define policy based on process events including process/thread
creation and exit.
- Ability to take action whenever an event occurs.
- Ability to set the CPU cycle threshold to a resolution of one millisecond.
Please review and tell me what you think.
Thanks.
Hirofumi Nakagawa
reply other threads:[~2008-05-22 10:06 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=48354469.40100@miraclelinux.com \
--to=hnakagawa@miraclelinux.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.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.