Received: by 10.223.176.5 with SMTP id f5csp1867000wra; Wed, 31 Jan 2018 12:51:11 -0800 (PST) X-Google-Smtp-Source: AH8x226E2dHU1cAWu7hKRAPX0JFlqIEFdMqcxt38OU5b1ziIiQrcfnCwdrn07C9SW3ar/2DcGpYf X-Received: by 10.99.130.66 with SMTP id w63mr26857796pgd.267.1517431871647; Wed, 31 Jan 2018 12:51:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517431871; cv=none; d=google.com; s=arc-20160816; b=y5PWFm1++vWdJJXKcj40lN69yptCJOT5oiXpW9+uSr3FNEFVGGZKsLJhx2Vvr7PefT GDue62PKrdlk/JneOy5Anq27s2EsQBYXhWNUB4I37+K3cCka13OWWoHmJ2cpGApK9FdO gj+j5KLHBZyJFr12He6E2ZQa9KdGNvwddj1dqAQDNEmbpE+6YwM4IC+2lKipIm+j78Hx BElpWR1bA3CO+uzpE32Nd3YDiTHzG63ZuOC6MTpZ2eRJWV/KftAr87edM4dsFu1Hoj9k DdU5n9j3FKO4IA/5qpeBQPkYiVrzN40uW27RPwu/c2zVsylsIONNjKYxPbsLFP94CRen SY8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:cc:references:to:subject:arc-authentication-results; bh=1EhM8XYM5lQbx+H/JInGPhMOgC3/qSchoq622dKOsgA=; b=ALVQ7y0DBVhuATDojaCckYppohLQeVi5TxERwKSCucj7O00DVnA3ZPW7zYZe7AJc2h 3uX+sl2oGjkF9GG0KJT3gNowIi1qTuXzfjN4X3kT/+DYOuLHEMLCIA/dhCrTmPRngv/4 2Pswvx98AoGyRK9GcuCubI6zPrp7kQXnpZMsvpANTLm7VLVYxm4Yp5NQe+vhX+7KhKdw hJCr5ofNgtT+AnKkBle4psIurMzjI1qa4Yi1ANEPs3+Nnq2WwSagOfWhoc4wOllLwm4O 8FqcbCn/g+5DneLVCwmpj1xBsSrZJUeYdhexFlFXXsIJcF0PQ5WhMi6iAvNCDo2F652E UHag== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p2si441417pgr.379.2018.01.31.12.50.56; Wed, 31 Jan 2018 12:51:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751868AbeAaUtt (ORCPT + 99 others); Wed, 31 Jan 2018 15:49:49 -0500 Received: from mga11.intel.com ([192.55.52.93]:17074 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751602AbeAaUts (ORCPT ); Wed, 31 Jan 2018 15:49:48 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jan 2018 12:49:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,441,1511856000"; d="scan'208";a="170687924" Received: from ray.jf.intel.com (HELO [10.7.201.20]) ([10.7.201.20]) by orsmga004.jf.intel.com with ESMTP; 31 Jan 2018 12:49:48 -0800 Subject: Re: [PATCH] x86: Align TLB invalidation info To: Nadav Amit , Andy Lutomirski References: <20180131201118.1694-1-namit@vmware.com> <747E60F0-2315-4BEC-895E-0E29C57A0AF0@gmail.com> Cc: x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , linux-kernel@vger.kernel.org, Peter Zijlstra , Andy Lutomirski From: Dave Hansen Message-ID: <1e0c2666-d0ee-8fe2-3272-6b49bf045834@linux.intel.com> Date: Wed, 31 Jan 2018 12:49:47 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <747E60F0-2315-4BEC-895E-0E29C57A0AF0@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/31/2018 12:48 PM, Nadav Amit wrote: >>> On Jan 31, 2018, at 12:11 PM, Nadav Amit wrote: >>> >>> The TLB invalidation info is allocated on the stack, which might cause >>> it to be unaligned. Since this information may be transferred to >>> different cores for TLB shootdown, this might result in an additional >>> cache-line bouncing between the cores. >>> >>> GCC provides a way to deal with it by using >>> __builtin_alloca_with_align(). Use it to avoid the bouncing cache lines. >> Eww. How about __aligned? > Err.. Stupid me. For some reason I remembered I tried it and it didn’t have > the desired effect, which caused me to assume it does not work for variables > on the stack. Anyhow, it does the work. I’ll submit v2. Also, just curious, but did you find this situation by inspection or did it show up in a profile somewhere?