From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756775Ab0HaJQE (ORCPT ); Tue, 31 Aug 2010 05:16:04 -0400 Received: from casper.infradead.org ([85.118.1.10]:52125 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756689Ab0HaJQC convert rfc822-to-8bit (ORCPT ); Tue, 31 Aug 2010 05:16:02 -0400 Subject: Re: [PATCH 08/20] powerpc: Preemptible mmu_gather From: Peter Zijlstra To: Benjamin Herrenschmidt Cc: Andrea Arcangeli , Avi Kivity , Thomas Gleixner , Rik van Riel , Ingo Molnar , akpm@linux-foundation.org, Linus Torvalds , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, David Miller , Hugh Dickins , Mel Gorman , Nick Piggin , Paul McKenney , Yanmin Zhang , Stephen Rothwell In-Reply-To: <1283236265.2151.35.camel@pasglop> References: <20100828141637.421594670@chello.nl> <20100828142455.960494507@chello.nl> <1283236004.2151.33.camel@pasglop> <1283236265.2151.35.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Tue, 31 Aug 2010 11:14:44 +0200 Message-ID: <1283246084.2059.66.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2010-08-31 at 16:31 +1000, Benjamin Herrenschmidt wrote: > Of course, with -rt and the pte lock becoming a mutex, all of your > changes do become necessary (and I suppose that's where they come from). > > Now, those changes won't technically hurt on a non-rt kernel, tho they > will add a tiny bit of overhead. I'll see if I can measure it. Indeed, those parts are only strictly needed for -rt, I was hoping the tiny bit of overhead wouldn't be too bad and we could keep it. If not I guess we should put those two bits in __switch_to() under CONFIG_PREEMPT_RT and carry them there for a little while longer. > > I suppose that's what's causing the similar patch you have in -rt to > > fail btw. This could be fixed easily by using "current" instead. > > And here's a fix. Using current_thread_info() everywhere is better > anyways, you are not supposed to touch the local_flags within anything > but "current" so we may as well make it explicit. > > Feel free to fold that into your -rt patch and this one if you decide > not to drop that whole part. Thanks! And yeah I'd prefer to keep it to reduce Thomas' burden if possible.