All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hirofumi Nakagawa <hnakagawa@miraclelinux.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [RFC][PATCH 0/1] MAZE: Mazed processes monitor
Date: Thu, 22 May 2008 18:31:12 +0900	[thread overview]
Message-ID: <48353D60.2050704@miraclelinux.com> (raw)
In-Reply-To: <20080513084157.098ae2dc.akpm@linux-foundation.org>

Hi Andrew,

Thank you for your comment and review.

> The immediate quesstion is, of course, "why does this need to be done
> in-kernel?".  I am unable to answer that from the provided changelog
> information, and I should be able to do that.

It needs to be done in kernel because excessive CPU cycle usage
is directly detected watching kernel internal task_struct.state.
It's hard to get that information outside the kernel.

Additionally, this patch's aim is to implement a
CGL (Carrier Grade Linux) requirement (AVL.14.0).

There are specs that can not be implemented outside the kernel.
These are;
  - Communication between the monitoring process and the kernel
  - Ability to define policy based on process events including
    process/thread creation and exit, and,
  - Ability to set the CPU cycle threshold to a resolution of
    one millisecond.

Thanks.
Hirofumi Nakagawa



  reply	other threads:[~2008-05-22  9:36 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 [this message]
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=48353D60.2050704@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.