From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Paul Menage <menage@google.com>
Cc: Matt Helsley <matthltc@us.ibm.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Arjan van de Ven <arjan@linux.intel.com>,
container cgroup <containers@lists.linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>,
akpm@linux-foundation.org, rdunlap@xenotime.net,
Cedric Le Goater <clg@vnet.ibm.com>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH 1/1, v9] cgroup/freezer: add per freezer duty ratio control
Date: Fri, 25 Feb 2011 10:23:19 -0800 [thread overview]
Message-ID: <20110225102319.6c776838@putvin> (raw)
In-Reply-To: <AANLkTinyhp29X8-atA=0DaHFuthTjVMJgBOitP52gwEX@mail.gmail.com>
On Fri, 25 Feb 2011 09:53:59 -0800
Paul Menage <menage@google.com> wrote:
> On Thu, Feb 24, 2011 at 3:45 PM, jacob pan
> <jacob.jun.pan@linux.intel.com> wrote:
> > I played with v3 and v4 of the CFS bandwidth patch. When the cpu
> > cgroup exceeds its cfs_quota, it does have the same effect as this
> > patch in terms of freeze/thaw at given period and allowed runtime.
> > But when the cgroup cpu usage is below cfs_quota, it is not
> > throttled. Therefore, it cannot reduce wakeups.
>
> How about a userspace daemon that periodically flips the CPU quota for
> the cgroup between zero and the group's runnable level? Wouldn't that
> achieve what you need pretty easily without having to introduce
> additional complexity and threads into the kernel?
I think it should work but with little bit more overhead than
doing the same in the kernel. It will also need one periodic timer per
cgroup. Two extra timer wake ups for each time slice to run.
Thanks for the great suggestion. I will do some experiment with it.
prev parent reply other threads:[~2011-02-25 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 22:09 [PATCH 0/1, v9] cgroup/freezer: add per freezer duty ratio control jacob.jun.pan
2011-02-15 22:09 ` [PATCH 1/1, " jacob.jun.pan
2011-02-16 0:00 ` Rafael J. Wysocki
2011-02-16 0:38 ` Jacob Pan
2011-02-16 3:23 ` Matt Helsley
2011-02-16 18:18 ` Jacob Pan
2011-02-24 23:45 ` jacob pan
2011-02-25 17:53 ` Paul Menage
2011-02-25 18:23 ` Jacob Pan [this message]
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=20110225102319.6c776838@putvin \
--to=jacob.jun.pan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=clg@vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=lizf@cn.fujitsu.com \
--cc=matthltc@us.ibm.com \
--cc=menage@google.com \
--cc=rdunlap@xenotime.net \
--cc=rjw@sisk.pl \
/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