From: Shailabh Nagar <nagar@watson.ibm.com>
To: ckrm-tech <ckrm-tech@lists.sourceforge.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: ckrm-e17
Date: Thu, 27 Jan 2005 12:52:08 -0500 [thread overview]
Message-ID: <41F92A48.2010100@watson.ibm.com> (raw)
Version e17 of the Class-based Kernel Resource Management
is now available for download from
http://sourceforge.net/project/showfiles.php?group_id=85838&package_id=94608
The major updates since the previous version include:
1. Numerous bugfixes
2. Control over rate of process forks through the numtasks controller.
The rate of forking is a single systemwide parameter affecting all
classes. Existing share-based control over total number of forks allowed
per class remains the same.
3. Interface change: The "target" file has been removed from the RCFS
interface. The same functionality can now be obtained by writing to the
"members" file of any class.
Files released:
ckrm-e17.2610.patch
Combined patch against 2.6.10. Includes the numtasks and
listenaq controllers.
e17-incr.tar.bz2
Tarball of broken down patches. First 10 patches constitute
the e16 release and subsequent ones contain the updates since
then.
cpu.ckrm-e17.v10.patch
CPU controller.
Still to come:
memory controller
I/O controller
test packages
Please note that updates to CKRM based on the feedback from lkml on
the previous release (http://lkml.org/lkml/2004/11/29/152) are in
progress and will be included in the next release.
Testing and feedback welcome.
--Shailabh
next reply other threads:[~2005-01-27 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 17:52 Shailabh Nagar [this message]
2005-01-27 18:33 ` ckrm-e17 Dave Hansen
2005-01-27 19:55 ` ckrm-e17 Shailabh Nagar
2005-02-12 5:48 ` ckrm-e17 Peter Williams
2005-02-12 17:47 ` ckrm-e17 Shailabh Nagar
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=41F92A48.2010100@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