public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Shailabh Nagar <nagar@watson.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	ckrm-tech <ckrm-tech@lists.sourceforge.net>
Subject: Re: [RFC] Revised CKRM release
Date: Tue, 4 May 2004 14:35:29 -0300	[thread overview]
Message-ID: <20040504173529.GE11346@logos.cnet> (raw)
In-Reply-To: <4090BBF1.6080801@watson.ibm.com>


On Thu, Apr 29, 2004 at 04:25:21AM -0400, Shailabh Nagar wrote:
> The Class-based Resource Management project is happy to release the
> first bits of a working prototype following a major revision of its
> interface and internal organization.
>
> The basic concepts and motivation of CKRM remain the same as described
> in the overview at http://ckrm.sf.net. Privileged users can define
> classes consisting of groups of kernel objects (currently tasks and
> sockets) and specify shares for these classes. Resource controllers,
> which are independent of each other, can regulate and monitor the
> resources consumed by classes e.g the CPU controller will control the
> CPU time received by a class etc. Optional classification engines,
> implemented as kernel modules, can assist in the automatic
> classification of the kernel objects (tasks/sockets currently) into
> classes.

Cool!

> New in this release are the following:
> 
> rbce.ckrm-E12:
> 
> Two classification engines (CE) to assist in automatic classification
> of tasks and sockets. The first one, rbce, implements a rule-based
> classification engine which is generic enough for most users. The
> second, called crbce, is a variant of rbce which additionally provides
> information on significant kernel events (where a task/socket could
> get reclassified) to userspace as well as reports per-process wait
> times for cpu, memory, io etc. Such information can be used by user
> level tools to reclassify tasks to new classes, change class shares
> etc.

It sounds to me the classification engine can be moved to userspace? 

Such "classification" sounds a better suited to be done there.

Note: I haven't read the code yet.

  parent reply	other threads:[~2004-05-04 17:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29  8:25 [RFC] Revised CKRM release Shailabh Nagar
2004-04-30 16:41 ` Christoph Hellwig
2004-04-30 18:42   ` Shailabh
2004-04-30 19:03   ` [ckrm-tech] " Rik van Riel
2004-04-30 19:17     ` Shailabh Nagar
2004-04-30 19:31       ` Rik van Riel
2004-04-30 20:15         ` Shailabh Nagar
2004-05-01 13:07         ` Hubertus Franke
2004-04-30 22:43       ` Jeff Dike
2004-04-30 19:47     ` Shailabh
2004-04-30 22:17       ` Jeff Dike
2004-04-30 23:43         ` Herbert Poetzl
2004-05-01  6:10           ` Alex Lyashkov
2004-05-01 14:46             ` Herbert Poetzl
2004-05-02 12:28               ` Alex Lyashkov
2004-05-04 17:29   ` Marcelo Tosatti
2004-05-04 18:13     ` [ckrm-tech] " Hubertus Franke
2004-05-04 17:35 ` Marcelo Tosatti [this message]
2004-05-05  0:18   ` Shailabh Nagar
2004-05-05 18:48     ` Marcelo Tosatti
2004-05-06  0:00       ` Chandra Seetharaman

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=20040504173529.GE11346@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nagar@watson.ibm.com \
    /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