From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932404Ab2BBPfO (ORCPT ); Thu, 2 Feb 2012 10:35:14 -0500 Received: from e36.co.us.ibm.com ([32.97.110.154]:47515 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932081Ab2BBPfL (ORCPT ); Thu, 2 Feb 2012 10:35:11 -0500 Date: Thu, 2 Feb 2012 07:34:37 -0800 From: "Paul E. McKenney" To: Avi Kivity Cc: Christoph Lameter , Peter Zijlstra , Gilad Ben-Yossef , linux-kernel@vger.kernel.org, Chris Metcalf , Frederic Weisbecker , linux-mm@kvack.org, Pekka Enberg , Matt Mackall , Sasha Levin , Rik van Riel , Andi Kleen , Mel Gorman , Andrew Morton , Alexander Viro , Michal Nazarewicz , Kosaki Motohiro , Milton Miller Subject: Re: [v7 0/8] Reduce cross CPU IPI interference Message-ID: <20120202153437.GD2518@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <1327572121-13673-1-git-send-email-gilad@benyossef.com> <1327591185.2446.102.camel@twins> <1328117722.2446.262.camel@twins> <20120201184045.GG2382@linux.vnet.ibm.com> <20120201201336.GI2382@linux.vnet.ibm.com> <4F2A58A1.90800@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F2A58A1.90800@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Content-Scanned: Fidelis XPS MAILER x-cbid: 12020215-3352-0000-0000-0000025802BA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 02, 2012 at 11:34:25AM +0200, Avi Kivity wrote: > On 02/01/2012 10:13 PM, Paul E. McKenney wrote: > > > > > > Could we also apply the same approach to processors busy doing > > > computational work? In that case the OS is also not needed. Interrupting > > > these activities is impacting on performance and latency. > > > > Yep, that is in fact what Frederic's dyntick-idle userspace work does. > > Running in a guest is a special case of running in userspace, so we'd > need to extend this work to kvm as well. As long as rcu_idle_enter() is called at the appropriate time, RCU will happily ignore the CPU. ;-) Thanx, Paul