Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758071AbbKSJeh (ORCPT ); Thu, 19 Nov 2015 04:34:37 -0500 Received: from mail1.bemta7.messagelabs.com ([216.82.254.109]:50837 "EHLO mail1.bemta7.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757711AbbKSJeb (ORCPT ); Thu, 19 Nov 2015 04:34:31 -0500 X-Greylist: delayed 412 seconds by postgrey-1.27 at vger.kernel.org; Thu, 19 Nov 2015 04:34:31 EST X-Env-Sender: Marc_Gonzalez@sigmadesigns.com X-Msg-Ref: server-4.tower-96.messagelabs.com!1447925255!8496260!1 X-Originating-IP: [195.215.56.170] X-StarScan-Received: X-StarScan-Version: 7.19.2; banners=-,-,- X-VirusChecked: Checked Subject: Re: [PATCH] clocksource: Store reg field within struct clocksource To: Russell King - ARM Linux CC: Thomas Gleixner , Daniel Lezcano , LKML , Mans Rullgard , Viresh Kumar , Nicolas Pitre , Tony Lindgren , Sebastian Frias References: <564C8086.80804@sigmadesigns.com> <20151118172114.GS8644@n2100.arm.linux.org.uk> From: Marc Gonzalez Message-ID: <564D9605.4010207@sigmadesigns.com> Date: Thu, 19 Nov 2015 10:27:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38 MIME-Version: 1.0 In-Reply-To: <20151118172114.GS8644@n2100.arm.linux.org.uk> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [172.27.0.114] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1458 Lines: 37 On 18/11/2015 18:21, Russell King - ARM Linux wrote: > On Wed, Nov 18, 2015 at 02:43:34PM +0100, Marc Gonzalez wrote: > >> Since 'struct clocksource' is ____cacheline_aligned, gcc must insert >> a lot of padding between reg and clksrc in 'struct clocksource_mmio' >> (for example, L1_CACHE_BYTES = 64 on ARMv7). >> >> Storing reg within 'struct clocksource' removes unnecessary padding, >> and reg can then be grouped with other hot data. A nice side-effect >> of this patch is making container_of() unnecessary, which makes the >> code a bit simpler. >> >> On 32-bit platforms, reg fits in the padding between read and mask, >> meaning no downside from storing it there. > > Just swap the order of 'reg' and 'clksrc'. You already suggested that the last time (April 1st). What problem is this supposed to solve? Swapping the fields does not change the amount of padding required, and does not place reg close to the hot data. On a 32-bit platform, with L1_CACHE_BYTES = 64 sizeof(struct unaligned_clocksource) = 80 sizeof(struct clocksource) = 128 sizeof(struct clocksource_mmio) = 192, reg at +0, clksrc at +64 sizeof(struct clocksource_mmio2) = 192, reg at +128, clksrc at +0 Same amount of padding. -- 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/