From: Andrew Morton <akpm@osdl.org>
To: "Marc E. Fiuczynski" <mef@CS.Princeton.EDU>
Cc: gh@us.ibm.com, linux-kernel@vger.kernel.org, riel@redhat.com,
mason@suse.com, ckrm-tech@lists.sourceforge.net,
llp@CS.Princeton.EDU, acb@CS.Princeton.EDU,
mlhuang@CS.Princeton.EDU, smuir@CS.Princeton.EDU
Subject: Re: [ckrm-tech] Re: [PATCH] CKRM: 0/10 Class Based Kernel Resource Management
Date: Fri, 3 Dec 2004 16:40:34 -0800 [thread overview]
Message-ID: <20041203164034.2191957c.akpm@osdl.org> (raw)
In-Reply-To: <NIBBJLJFDHPDIBEEKKLPMEBMCOAA.mef@cs.princeton.edu>
"Marc E. Fiuczynski" <mef@CS.Princeton.EDU> wrote:
>
> I integrated CKRM with the kernel used by PlanetLab (www.planet-lab.org),
> and I believe we (PlanetLab) are the first to use CKRM in a production
> setting.
> ...
> Hope this helps.
It does, thanks.
A concern which I have about the CKRM implementation is that the patches
which have been sent out appear to be simply the "core" of CKRM, plus
minimally-intrusive hooks. I have the impression that this core will not
be terribly useful to real-world users and that follow-on patches will be
required to add more functionality and to wire up more instrumentation and
control points.
I would not like to be in a situation where we merge the "core" patch, but
the as-yet-unseen follow-on patches which make CKRM useful and complete end
up creating a big unmaintainable mess. We end up not wanting to go
forwards and being unable to go backwards.
IOW: I think we need to see a reasonably-close-to-final implementation of
CKRM before we can take it much further.
next prev parent reply other threads:[~2004-12-04 0:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:44 Gerrit Huizenga
2004-11-29 20:23 ` Andrew Morton
2004-11-29 22:33 ` Gerrit Huizenga
2004-12-03 11:54 ` [ckrm-tech] " Marc E. Fiuczynski
2004-12-04 0:40 ` Andrew Morton [this message]
2004-12-04 8:33 ` Gerrit Huizenga
2004-12-06 6:30 ` Andrew Morton
2004-11-29 22:32 ` Christoph Hellwig
2004-11-29 22:51 ` Gerrit Huizenga
2004-11-30 8:55 ` Nikita Danilov
2004-11-30 2:43 ` Greg KH
2004-11-30 2:48 ` Gerrit Huizenga
2004-11-30 4:07 ` Greg KH
2004-11-30 5:59 ` Gerrit Huizenga
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=20041203164034.2191957c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=acb@CS.Princeton.EDU \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llp@CS.Princeton.EDU \
--cc=mason@suse.com \
--cc=mef@CS.Princeton.EDU \
--cc=mlhuang@CS.Princeton.EDU \
--cc=riel@redhat.com \
--cc=smuir@CS.Princeton.EDU \
/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®