mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Gerrit Huizenga <gh@us.ibm.com>
Cc: pj@engr.sgi.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
	ckrm-tech@lists.sourceforge.net
Subject: Re: [patch 0/8] CKRM: Core patch set
Date: Thu, 31 Mar 2005 00:29:00 +0200	[thread overview]
Message-ID: <20050331002900.5c5dd04a.diegocg@gmail.com> (raw)
In-Reply-To: <E1DGkl7-0002aV-00@w-gerrit.beaverton.ibm.com>

El Wed, 30 Mar 2005 13:29:53 -0800,
Gerrit Huizenga <gh@us.ibm.com> escribió:

> been under so much revision lately.  However, resource utilization at the
> priority level does not allow you to say "OpenOffice can have up to 30%
> of my CPU, my email client is guaranteed to get at least 5%, and Firefox +
> Java apps get no more than 50% of my machine, and my CD player gets 10%".
> Niceness levels provide none of that level of resource control.  Also,

Users can launch tasks and renice them to lowest priority levels..., with the highset
priority being given by the administrator...I've always though it's gnome/kde fault to launch
the apps at the same nice level than the panel and the window manager. Despite of 
that my "design" wouldn't achieve that such fine-grained control, no - I'd argue that not
many people needs that, but then I shouldn't tell people what they need (and anyway
the previous proposal would so powerful for its simplicity that it might be worth of it doing
it anyway)

>  I'd love to see patches which could be validated by folks like the PlanetLab
>  folks, for instance.  I don't believe it is possible to get the level of machine
>  partitioning/virtualization that CKRM provides with this overly simple prioritization
>  scheme.

I realize that CKRM provides much broader functionality, the alternative I was proposing
was just for CPU resources (and would probably work well for IO bandwith with CFQ),
I realize that things like "partitioning memory resources" is a whole different problem.

But I certainly think that CKRM is far too complex - the docs I've read spent all the time
describing things like classes, classes inhretance, classification engine, resources
scheduler, resource schedulers configuration and so on. I must admit I've not read too
much about CKRM - I had to stop because I couldn't understand it, everything is far too
complex to my little mind, and I'm saying this because I bet I'm not the only one here
who can't understand it either.....

  reply	other threads:[~2005-03-30 22:29 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 [this message]
2005-03-31  1:32         ` Paul Jackson
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=20050331002900.5c5dd04a.diegocg@gmail.com \
    --to=diegocg@gmail.com \
    --cc=akpm@osdl.org \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=gh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@engr.sgi.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

Powered by JetHome