From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756911Ab2EHPsg (ORCPT ); Tue, 8 May 2012 11:48:36 -0400 Received: from merlin.infradead.org ([205.233.59.134]:47960 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756469Ab2EHPsd convert rfc822-to-8bit (ORCPT ); Tue, 8 May 2012 11:48:33 -0400 Message-ID: <1336492081.8226.13.camel@twins> Subject: Re: [PATCH 07/41] cpuset: Set up interface for nohz flag From: Peter Zijlstra To: Christoph Lameter Cc: Frederic Weisbecker , LKML , linaro-sched-sig@lists.linaro.org, Alessio Igor Bogani , Andrew Morton , Avi Kivity , Chris Metcalf , Daniel Lezcano , Geoff Levand , Gilad Ben Yossef , Hakan Akkan , Ingo Molnar , Kevin Hilman , Max Krasnyansky , "Paul E. McKenney" , Stephen Hemminger , Steven Rostedt , Sven-Thorsten Dietrich , Thomas Gleixner Date: Tue, 08 May 2012 17:48:01 +0200 In-Reply-To: References: <1335830115-14335-1-git-send-email-fweisbec@gmail.com> <1335830115-14335-8-git-send-email-fweisbec@gmail.com> <1336488626.16236.41.camel@twins> <1336490832.8226.5.camel@twins> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2012-05-08 at 10:38 -0500, Christoph Lameter wrote: > On Tue, 8 May 2012, Peter Zijlstra wrote: > > > isolating how? The only way to do that is with the (broken) isolcpus > > crap and cpusets. There is no other way. > > For some reason this seems to work here. What is broken with isolcpus? It mostly still works I think, but iirc there were a few places that ignored the cpuisol mask. But really the moment we get proper means of flushing cpu state (currently achievable by unplug-replug) isolcpu gets depricated and eventually removed. cpusets can do what isolcpu can and more (provided this flush thing). > > Furthermore there is no other partitioning scheme, cpusets is it. > > One can partition the system anyway one wants by setting cpu affinities > and memory policies etc. No need for cpusets/cgroups. Not so, the load-balancer will still try to move the tasks and subsequently fail. Partitioning means it won't even try to move tasks across the partition boundary. By proper partitioning you can split load balance domains (or completely disable the load-balancer by giving it a single cpu domain).