From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755906Ab2EHOvN (ORCPT ); Tue, 8 May 2012 10:51:13 -0400 Received: from merlin.infradead.org ([205.233.59.134]:51419 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755334Ab2EHOvM convert rfc822-to-8bit (ORCPT ); Tue, 8 May 2012 10:51:12 -0400 Message-ID: <1336488626.16236.41.camel@twins> Subject: Re: [PATCH 07/41] cpuset: Set up interface for nohz flag From: Peter Zijlstra To: Frederic Weisbecker Cc: Christoph Lameter , 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 16:50:26 +0200 In-Reply-To: References: <1335830115-14335-1-git-send-email-fweisbec@gmail.com> <1335830115-14335-8-git-send-email-fweisbec@gmail.com> 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 16:20 +0200, Frederic Weisbecker wrote: > 2012/5/7 Christoph Lameter : > > On Tue, 1 May 2012, Frederic Weisbecker wrote: > > > >> Prepare the interface to implement the nohz cpuset flag. > >> This flag, once set, will tell the system to try to > >> shutdown the periodic timer tick when possible. > >> > >> We use here a per cpu refcounter. As long as a CPU > >> is contained into at least one cpuset that has the > >> nohz flag set, it is part of the set of CPUs that > >> run into adaptive nohz mode. > > > > As I have said before: It would be much simpler if one could specify the > > set of nohz cpus independently of cpusets. Having a flag f.e. as a file in > > > > /sys/devices/system/cpu/cpuX/nohz > > I don't know if it would be simpler. It's just a different interface > to set a per-CPU property. > Cpusets of sysfs, I don't mind either way. > > What is the usual policy on where to put which kind of CPU property? There's no such policy, but I don't get why Christoph objects to cpusets, its the option I would prefer. You're going to use cpusets anyway to partition your system, might as well also use it to mark a whole partition/set as nohz.