From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760772Ab2FDVIU (ORCPT ); Mon, 4 Jun 2012 17:08:20 -0400 Received: from e39.co.us.ibm.com ([32.97.110.160]:50045 "EHLO e39.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754128Ab2FDVIS (ORCPT ); Mon, 4 Jun 2012 17:08:18 -0400 Date: Mon, 4 Jun 2012 14:07:09 -0700 From: "Paul E. McKenney" To: Frederic Weisbecker Cc: Ingo Molnar , LKML , Alessio Igor Bogani , Andrew Morton , Avi Kivity , Chris Metcalf , Christoph Lameter , Daniel Lezcano , Geoff Levand , Gilad Ben Yossef , Hakan Akkan , Kevin Hilman , Max Krasnyansky , Peter Zijlstra , Stephen Hemminger , Steven Rostedt , Sven-Thorsten Dietrich , Thomas Gleixner Subject: Re: [PATCH 0/2] rcu: Extended quiescent state for adaptive nohz Message-ID: <20120604210709.GO2490@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <1338811708-18819-1-git-send-email-fweisbec@gmail.com> <20120604181313.GL2490@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Content-Scanned: Fidelis XPS MAILER x-cbid: 12060421-4242-0000-0000-000001DDD85B Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 04, 2012 at 09:06:22PM +0200, Frederic Weisbecker wrote: > 2012/6/4 Paul E. McKenney : > > On Mon, Jun 04, 2012 at 02:08:26PM +0200, fweisbec@gmail.com wrote: > >> From: Frederic Weisbecker > >> > >> Paul, Ingo, > >> > >> This is a rebase of the nohz cpusets RCU APIs on top of Paul's latest > >> -rcu (rcu/core) branch. > >> > >> I have only built tested it yet, I need to do a full rebase of my > >> tree to test it in practice. But I wanted to show you how it looks > >> like first. > >> > >> I also wonder if we can set that to a tree somewhere. Ingo suggested > >> to set up a tree on -tip to apply the uncontroversial part of nohz > >> cpusets patches and iterate from there. I think it would accelerate > >> everything if we start doing that. > > > > It would probably be best to put these two in the -rcu set in order to > > avoid conflicts with possible further RCU_FAST_NO_HZ work.  I could > > push this to -tip early, if that would help. > > But then these APIs are going to be upstream on 3.6 > Is that ok for you even if they don't have any upstream user? > We can ifdef it. I figured on maintaining a separate rcu/idle topic branch that I would merge locally for building and testing, but which I would not push to rcu/next. If Ingo agrees, I can push separately to -tip so that it does not go upstream until you are ready, at which point I would merge it into rcu/next. Seem reasonable, or would something else work better? Thanx, Paul