From: Peter Williams <peterw@aurema.com>
To: balbir@in.ibm.com
Cc: Peter Williams <pwil3058@bigpond.net.au>,
Andrew Morton <akpm@osdl.org>,
dev@openvz.org, vatsa@in.ibm.com,
ckrm-tech@lists.sourceforge.net, bsingharora@gmail.com,
efault@gmx.de, linux-kernel@vger.kernel.org, kernel@kolivas.org,
sam@vilain.net, kingsley@aurema.com, mingo@elte.hu,
rene.herman@keyaccess.nl
Subject: Re: [ckrm-tech] [PATCH 0/4] sched: Add CPU rate caps
Date: Tue, 20 Jun 2006 09:09:39 +1000 [thread overview]
Message-ID: <44972EB3.8090400@aurema.com> (raw)
In-Reply-To: <44968B6D.8040301@in.ibm.com>
Balbir Singh wrote:
> Peter Williams wrote:
>
>>
>> You're over engineering and you're not solving the problem. You're
>> just moving it down a bit.
>>
>
>>
>>>
>>> 2. In a group based cap management system, schedule some tasks
>>> (highest priority)
>>> until their cap run out. In the subsequent rounds pick and choose
>>> tasks that
>>> did not get a chance to run earlier.
>>>
>>> Solving this is indeed a interesting problem.
>>>
>>
>>
>> Once again, you're over engineering and probably making the problem
>> worse.
>>
>
> I like this term over-engineering. Lets focus on the solution for the most
> common case and see what works out. I was pointing you to the possible
> limitations of the approach, which is always a good thing to do in
> engineering.
And I was pointing out that it's a fundamental limitation that can't be
avoided no matter which implementation route you follow.
Peter
--
Dr Peter Williams, Chief Scientist <peterw@aurema.com>
Aurema Pty Limited
Level 2, 130 Elizabeth St, Sydney, NSW 2000, Australia
Tel:+61 2 9698 2322 Fax:+61 2 9699 9174 http://www.aurema.com
next prev parent reply other threads:[~2006-06-19 23:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 8:26 [PATCH 0/4] sched: Add CPU rate caps Peter Williams
2006-06-18 8:26 ` [PATCH 1/4] sched: Add CPU rate soft caps Peter Williams
2006-06-18 8:38 ` Con Kolivas
2006-06-18 15:52 ` Peter Williams
2006-06-19 1:21 ` Peter Williams
2006-06-18 8:26 ` [PATCH 2/4] sched: Add CPU rate hard caps Peter Williams
2006-06-18 8:27 ` [PATCH 3/4] sched: Add procfs interface for CPU rate soft caps Peter Williams
2006-06-18 8:27 ` [PATCH 4/4] sched: Add procfs interface for CPU rate hard caps Peter Williams
2006-06-18 9:50 ` [PATCH 0/4] sched: Add CPU rate caps Andrew Morton
2006-06-18 10:25 ` Peter Williams
2006-06-18 11:42 ` Srivatsa Vaddagiri
2006-06-18 12:19 ` Peter Williams
2006-06-19 0:13 ` Balbir Singh
2006-06-19 1:03 ` [ckrm-tech] " Peter Williams
2006-06-19 2:20 ` Balbir Singh
2006-06-19 3:17 ` Peter Williams
2006-06-19 3:31 ` Balbir Singh
2006-06-19 3:50 ` Peter Williams
2006-06-19 8:30 ` Balbir Singh
2006-06-19 11:35 ` Peter Williams
2006-06-19 11:33 ` Balbir Singh
2006-06-19 23:09 ` Peter Williams [this message]
2006-06-20 4:28 ` Peter Williams
2006-06-20 4:40 ` Balbir Singh
2006-06-20 5:56 ` Peter Williams
2006-06-19 5:04 ` Peter Williams
2006-06-19 23:59 ` Peter Williams
2006-06-19 18:55 ` [ckrm-tech] " Chris Friesen
2006-06-19 23:28 ` Peter Williams
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=44972EB3.8090400@aurema.com \
--to=peterw@aurema.com \
--cc=akpm@osdl.org \
--cc=balbir@in.ibm.com \
--cc=bsingharora@gmail.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=dev@openvz.org \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--cc=kingsley@aurema.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pwil3058@bigpond.net.au \
--cc=rene.herman@keyaccess.nl \
--cc=sam@vilain.net \
--cc=vatsa@in.ibm.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