Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755194Ab1BYRyX (ORCPT ); Fri, 25 Feb 2011 12:54:23 -0500 Received: from smtp-out.google.com ([216.239.44.51]:51678 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751325Ab1BYRyW (ORCPT ); Fri, 25 Feb 2011 12:54:22 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=kPl6dWjEqxgeLDmDu8WRs/IkJcjdKOTdAjtXONPnLONOJIlTGn6eKDvlyrtFTRR/Bo lsW/Ti95MjXK33IKOahg== MIME-Version: 1.0 In-Reply-To: <20110224154525.1b463723@jacob-laptop> References: <1297807750-28844-1-git-send-email-jacob.jun.pan@linux.intel.com> <1297807750-28844-2-git-send-email-jacob.jun.pan@linux.intel.com> <201102160100.15487.rjw@sisk.pl> <20110215163812.7fa020b5@putvin> <20110216032321.GA14893@count0.beaverton.ibm.com> <20110224154525.1b463723@jacob-laptop> From: Paul Menage Date: Fri, 25 Feb 2011 09:53:59 -0800 Message-ID: Subject: Re: [PATCH 1/1, v9] cgroup/freezer: add per freezer duty ratio control To: jacob pan Cc: Matt Helsley , "Rafael J. Wysocki" , LKML , "Kirill A. Shutemov" , Arjan van de Ven , container cgroup , Li Zefan , akpm@linux-foundation.org, rdunlap@xenotime.net, Cedric Le Goater , Linux PM mailing list Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 907 Lines: 19 On Thu, Feb 24, 2011 at 3:45 PM, jacob pan 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? Paul -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/