Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934240AbbKSN6w (ORCPT ); Thu, 19 Nov 2015 08:58:52 -0500 Received: from www.linutronix.de ([62.245.132.108]:40571 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934173AbbKSN6P (ORCPT ); Thu, 19 Nov 2015 08:58:15 -0500 Date: Thu, 19 Nov 2015 14:57:30 +0100 (CET) From: Thomas Gleixner To: Marc Gonzalez cc: Russell King - ARM Linux , Daniel Lezcano , LKML , Mans Rullgard , Viresh Kumar , Nicolas Pitre , Tony Lindgren , Sebastian Frias Subject: Re: [PATCH] clocksource: Store reg field within struct clocksource In-Reply-To: <564DC006.8000406@sigmadesigns.com> Message-ID: References: <564C8086.80804@sigmadesigns.com> <20151118172114.GS8644@n2100.arm.linux.org.uk> <20151119103645.GV8644@n2100.arm.linux.org.uk> <20151119110842.GX8644@n2100.arm.linux.org.uk> <564DC006.8000406@sigmadesigns.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 780 Lines: 19 On Thu, 19 Nov 2015, Marc Gonzalez wrote: > On 19/11/2015 12:14, Thomas Gleixner wrote: > > > So yes, the alignment of the clocksource struct is not longer > > relevant. The case where we access clocksource->max_cycles is when > > CONFIG_DEBUG_TIMEKEEPING is enabled, which imposes worse performance > > problems to timekeeping than the extra cacheline. > > > > So the simple solution for this issue is indeed the one liner below. > > It would make sense to also remove the comment emphasizing the > alignment requirement. Indeed. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/