mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shailabh Nagar <nagar@watson.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: ckrm-tech@lists.sourceforge.net
Subject: [RFC] Class-based Kernel Resource Management
Date: 29 Aug 2003 15:51:48 -0400	[thread overview]
Message-ID: <1062186708.15245.832.camel@elinux05.watson.ibm.com> (raw)

As promised at the Ottawa Linux Symposium presentation in July, here
is the first code drop for the Class-based Kernel Resource Management
project.

The Class-based Kernel Resource Management (CKRM)
project seeks to develop Linux kernel mechanisms providing
differentiated service to resources such as CPU time, memory pages,
I/O and incoming network bandwith based on user defined groups of
tasks called classes. Changes to the primary resource schedulers such
as O(1) (cpu), deadline/CFQ (I/O) , VM page manager (memory) and
inbound network connection managers will be explored and developed.

More details on the project can be found at

	http://ckrm.sf.net

including 

- the paper and presentation at the Ottawa Linux Symposium 2003
- current status
- patches, modules, user programs
- detailed description of individual components and
- results from the version that was talked about at OLS'03.


The current CKRM design consists of the following components:

1) Core patch: Kernel patch defining kernel API and hooks for the
classification module and individual resource (cpu,mem,io,net)
controllers.  

2) Classification and user API module: Loadable module implementing a
Rule-based Classification Engine (RBCE) and defining a user API to
CKRM. Requires the core patch.  


3) CPU controller: Kernel patch implementing class-based CPU
control.Requires the core patch and some classification module like
RBCE.  

4) Memory controller: Kernel patch for class-based control of physical
memory.  Requires the core patch and some classification module like
RBCE.

5) I/O controller: Design proposed in OLS. To be developed in
conjunction with Jens Axboe's next version of CFQ I/O scheduler.

6) Inbound network controller: Design proposed. In development.

The next few mail will contain the patches for 1),3) and 4), the module
for 2).


If you are interested in this project, please join the ckrm-tech mailing
list at 
	http://lists.sourceforge.net/lists/listinfo/ckrm-tech

You are also welcome to join as a developer by sending a mail to the
project admins
Hubertus Franke (frankeh@users.sf.net) and Shailabh Nagar
(nagar@users.sf.net).

CKRM has been jointly developed by a number of folks including
Hubertus Franke, Shailabh Nagar, Chandra Seetharaman, Jiantao Kong,
Haoqiang Zheng, Vivek Kashyap, Nivedita Singhvi and Jonghyuk Choi.

 

-- Shailabh



             reply	other threads:[~2003-08-29 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 19:51 Shailabh Nagar [this message]
2003-09-03  1:54 ` NIWA Hideyuki
2003-09-03 19:20   ` Shailabh Nagar
2003-09-17  5:08     ` NIWA Hideyuki

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=1062186708.15245.832.camel@elinux05.watson.ibm.com \
    --to=nagar@watson.ibm.com \
    --cc=ckrm-tech@lists.sourceforge.net \
    --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

all inboxes | Powered by JetHome®