From: MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Kirill Korotaev <dev@openvz.org>, Srivatsa <vatsa@in.ibm.com>,
CKRM <ckrm-tech@lists.sourceforge.net>,
Balbir Singh <bsingharora@gmail.com>,
Mike Galbraith <efault@gmx.de>, Con Kolivas <kernel@kolivas.org>,
Sam Vilain <sam@vilain.net>,
Kingsley Cheung <kingsley@aurema.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>,
Rene Herman <rene.herman@keyaccess.nl>,
MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>
Subject: Re: [ckrm-tech] [RFC 0/4] sched: Add CPU rate caps (improved)
Date: Fri, 09 Jun 2006 14:41:06 +0900 [thread overview]
Message-ID: <448909F2.2060306@jp.fujitsu.com> (raw)
In-Reply-To: <4487D6B0.3080502@bigpond.net.au>
Peter Williams wrote:
> This behaviour is caused by the "make clean" being a short lived CPU
> intensive task. It was made worse by the facts that my simplifications
> to the sinbin duration calculation which assumed a constant CPU burst
> size based on the time slice and that exiting tasks could still have
> caps enforced. (The simplification was done to avoid 64 bit divides.)
>
> I've put in a more complex sinbin calculation (and don't think the 64
> bit divides will matter too much as they're on an infrequently travelled
> path. Exiting tasks are now excluded from having caps enforced on the
> grounds that it's best for system performance to let them get out of the
> way as soon as possible. A patch is attached and I would appreciate it
> if you could see if it improves the situation you are observing.
Sorry for my late reply.
The followings are the results of patched kernel. Unfortunately,
the patch doesn't seem to help my situation.
$ ~/withcap.sh -C 900 /usr/bin/time make clean
1.61user 0.29system 1:33.94elapsed 2%CPU
$ ~/withcap.sh -C 100 /usr/bin/time make clean
1.68user 0.27system 3:34.45elapsed 0%CPU
Thanks,
MAEDA Naoaki
next prev parent reply other threads:[~2006-06-09 5:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060606023708.2801.24804.sendpatchset@heathwren.pw.nest>
2006-06-07 8:05 ` [ckrm-tech] [RFC 0/4] sched: Add CPU rate caps (improved) MAEDA Naoaki
2006-06-07 12:44 ` Peter Williams
2006-06-08 7:50 ` Peter Williams
2006-06-09 0:57 ` Peter Williams
2006-06-09 5:50 ` MAEDA Naoaki
2006-06-09 6:05 ` Peter Williams
2006-06-09 5:41 ` MAEDA Naoaki [this message]
2006-06-09 6:38 ` 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=448909F2.2060306@jp.fujitsu.com \
--to=maeda.naoaki@jp.fujitsu.com \
--cc=bsingharora@gmail.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=dev@openvz.org \
--cc=ebiederm@xmission.com \
--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