From: Paul Jackson <pj@engr.sgi.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: gh@us.ibm.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
ckrm-tech@lists.sourceforge.net
Subject: Re: [patch 0/8] CKRM: Core patch set
Date: Wed, 30 Mar 2005 17:32:32 -0800 [thread overview]
Message-ID: <20050330173232.3ae4c791.pj@engr.sgi.com> (raw)
In-Reply-To: <20050331002900.5c5dd04a.diegocg@gmail.com>
Diego wrote:
> I bet I'm not the only one here
> who can't understand it either.....
You're not alone.
See an email thread entitled:
Classes: 1) what are they, 2) what is their name?
http://sourceforge.net/mailarchive/forum.php?thread_id=5328162&forum_id=35191
on the ckrm-tech@lists.sourceforge.net email list between Aug 14 and Aug
27, 2004, where I did my best to encourage the CKRM project to address
this problem. To no avail.
Apparently, to some of the smartest amongst us, who got to hear
live presentations describing CKRM, it makes sense and is worthy
of serious consideration.
For myself, of more ordinary intelligence and working just from the
documentation and an occassional glance at the code, it has been a
difficult proposal to understand, with a rather large patch requiring
some non-trivial kernel hooks.
A question for the CKRM developers:
What middleware packages, outside the kernel, exist or are
in the works that will rely on CKRM?
CKRM (like another project near and dear to me, cpusets)
strikes me as a "middleware foundation" facility, intended
to provide the essential kernel support required for some
serious enterprise software. So perhaps in addition to
asking what end-users (of a combined kernel-middleware
platform) exist, we should also be asking who will be
directly using CKRM - directly layering middleware on top
of it.
The details don't matter much and may have to remain
obscured in the competitive fog. But the presence of
multiple groups lobbying for the same kernel infrastructure,
as an apparent basis for competing middleware products,
would I think weigh in CKRM's favor.
My impression, which may not align with how the CKRM developers view
things, is that CKRM is descendent from what have been called fair-share
schedulers. The following comes from the above email thread.
No doubt the CKRM experts are already familiar with these, but for the
possible benefit of other readers:
UNICOS Resource Administration - Chapter 4. Fair-share Scheduler
http://oscinfo.osc.edu:8080/dynaweb/all/004-2302-001/@Generic__BookTextView/22883
SHARE II -- A User Administration and Resource Control System for UNIX
http://www.c-side.com/c/papers/lisa-91.html
Solaris Resource Manager White Paper
http://wwws.sun.com/software/resourcemgr/wp-mixed/
ON THE PERFORMANCE IMPACT OF FAIR SHARE SCHEDULING
http://www.cs.umb.edu/~eb/goalmode/cmg2000final.htm
A Fair Share Scheduler, J. Kay and P. Lauder
Communications of the ACM, January 1988, Volume 31, Number 1, pp 44-55.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
next prev parent reply other threads:[~2005-03-31 1:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 2:52 gh
2005-03-30 6:05 ` Paul Jackson
2005-03-30 7:03 ` Gerrit Huizenga
2005-03-30 16:57 ` Dave Hansen
2005-03-30 20:55 ` Diego Calleja
2005-03-30 21:29 ` Gerrit Huizenga
2005-03-30 22:29 ` Diego Calleja
2005-03-31 1:32 ` Paul Jackson [this message]
2005-03-31 3:30 ` Gerrit Huizenga
2005-03-31 14:46 ` [ckrm-tech] " Shailabh Nagar
2005-03-30 22:11 ` Shailabh Nagar
2005-03-31 0:25 ` Chandra Seetharaman
2005-03-30 20:55 ` Diego Calleja
[not found] <1112201599.11490.6.camel@localhost>
2005-03-30 17:25 ` Gerrit Huizenga
2005-03-30 18:48 ` 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=20050330173232.3ae4c791.pj@engr.sgi.com \
--to=pj@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=diegocg@gmail.com \
--cc=gh@us.ibm.com \
--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®