From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vivek Goyal Subject: Re: [PATCH cgroup/for-3.11 1/3] cgroup: mark "tasks" cgroup file as insane Date: Tue, 4 Jun 2013 10:34:44 -0400 Message-ID: <20130604143444.GI4799@redhat.com> References: <20130604021302.GH29989@mtj.dyndns.org> <20130604111556.GA4963@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20130604111556.GA4963-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Daniel P. Berrange" Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, kay.sievers-tD+1rO4QERM@public.gmane.org, Michal Hocko , lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org, Johannes Weiner , Tejun Heo , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Tue, Jun 04, 2013 at 12:15:56PM +0100, Daniel P. Berrange wrote: > On Mon, Jun 03, 2013 at 07:13:02PM -0700, Tejun Heo wrote: > > Some resources controlled by cgroup aren't per-task and cgroup core > > allowing threads of a single thread_group to be in different cgroups > > forced memcg do explicitly find the group leader and use it. This is > > gonna be nasty when transitioning to unified hierarchy and in general > > we don't want and won't support granularity finer than processes. > > With libvirt and KVM we require the ability to put different threads > in different cgroups for the "cpu", "cpuset" & "cpuacct" controllers. > This is to allow us to control schedular tunables / placement for > QEMU vCPU threads, independantly of limits for QEMU I/O threads. So > requiring all threads of a process to be in the same cgroup isn't > sufficiently flexible for our needs. For placement of vCPU threads, can we set per thread cpu affinity (sched_setaffinity()), instead of using cgroups for that purpose. Apart from cpu affinity, what scheduling parameters we want different between different threads. Thanks Vivek