From: Rik van Riel <riel@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [ckrm-tech] Re: [Lse-tech] Re: CPUSET Proposal
Date: Thu, 25 Sep 2003 16:06:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106450615513424@msgid-missing> (raw)
On Thu, 25 Sep 2003, Hubertus Franke wrote:
> Paul, yes CKRM classes at this point are flat, we looked initially at
> hierarchies and determined that for the first release might add a lot of
> complexity with questionable benefits for the community at large. So we
> left hierarchies out. Based on the general community feedback we might
> have to revisit this issue.
I'm not sure we will ever need hierarchies in the kernel.
For all intents and purposes, we might be able to emulate
them in userspace by having a daemon interpret the class
resource usage statistics and adjusting priorities
dynamically ;)
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
reply other threads:[~2003-09-25 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-106450615513424@msgid-missing \
--to=riel@redhat.com \
--cc=linux-ia64@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