From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH] re-order struct domain fields Date: Mon, 19 Jan 2015 16:25:13 +0000 Message-ID: <1421684713.10440.139.camel@eu.citrix.com> References: <54BD340602000078000568FB@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YDF8k-0006EF-Au for xen-devel@lists.xenproject.org; Mon, 19 Jan 2015 16:25:22 +0000 In-Reply-To: <54BD340602000078000568FB@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel , Keir Fraser , Ian Jackson , Tim Deegan List-Id: xen-devel@lists.xenproject.org On Mon, 2015-01-19 at 15:42 +0000, Jan Beulich wrote: > ... to reduce padding holes. > > I also wonder whether having independent spin locks side by side is > really a good thing cache-line-bouncing-wise. AIUI the general wisdom is to put each spinlock next to the data it protects (I suppose on the assumption that after acquiring the lock you will next touch that data). Is the problem is that the domain_lock doesn't actually protect anything in this struct since it is a more umbrella lock, so there is nothing to put next to it? You could move either it or the page lock below all the page counts stuff. Ian.