From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934589AbbDIJcH (ORCPT ); Thu, 9 Apr 2015 05:32:07 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:40460 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933710AbbDIJba (ORCPT ); Thu, 9 Apr 2015 05:31:30 -0400 Date: Thu, 9 Apr 2015 11:31:15 +0200 From: Peter Zijlstra To: Thomas Gleixner Cc: Ingo Molnar , Viresh Kumar , Ingo Molnar , linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org, Preeti U Murthy Subject: Re: [PATCH] hrtimer: Replace cpu_base->active_bases with a direct check of the active list Message-ID: <20150409093115.GQ5029@twins.programming.kicks-ass.net> References: <20150409062841.GB14259@gmail.com> <20150409065730.GK27490@worktop.programming.kicks-ass.net> <20150409070917.GF14259@gmail.com> <20150409072038.GA30205@gmail.com> <20150409085859.GN5029@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 09, 2015 at 11:18:52AM +0200, Thomas Gleixner wrote: > On Thu, 9 Apr 2015, Peter Zijlstra wrote: > > On Thu, Apr 09, 2015 at 09:20:39AM +0200, Ingo Molnar wrote: > > > if at least one base is active (on my fairly standard system all cpus > > > have at least one active hrtimer base all the time - and many cpus > > > have two bases active), then we run hrtimer_get_softirq_time(), which > > > dirties the cachelines of all 4 clock bases: > > > > > > base->clock_base[HRTIMER_BASE_REALTIME].softirq_time = xtim; > > > base->clock_base[HRTIMER_BASE_MONOTONIC].softirq_time = mono; > > > base->clock_base[HRTIMER_BASE_BOOTTIME].softirq_time = boot; > > > base->clock_base[HRTIMER_BASE_TAI].softirq_time = tai; > > > > > > so in practice we not only touch every cacheline in every timer > > > interrupt, but we _dirty_ them, even the inactive ones. > > > > > > > Urgh we should really _really_ kill that entire softirq mess. > > That's the !highres part. We cannot kill that one unless we remove all > support for machines which do not provide hardware for highres > support. Oops, sorry I mixed up the two. Doesn't take away from the fact that I'd like to get rid of the highres softirq fallback path.