Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp179002imm; Thu, 4 Oct 2018 21:03:03 -0700 (PDT) X-Google-Smtp-Source: ACcGV61AupHmfi7hYsiuJorJI4SPg2kGnFQDB680JsiM/rZMFqnY5XDP4iCcMo2wTS7dw+4TGXda X-Received: by 2002:a17:902:b03:: with SMTP id 3-v6mr2010270plq.141.1538712183187; Thu, 04 Oct 2018 21:03:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538712183; cv=none; d=google.com; s=arc-20160816; b=OLZ9kvUok6fWbrToGlkpUBk5AxoblpjMbmVDsngoIs0qoer0JTB66qnhTlpvP0loq9 C29sGNqocm3EDGa600riwhw9QYcfUoC+fMn4vzF6N7+nSivPfc2fx7MpcGoUUnr0zLOF 15d2mgjk35eokhrmt+XYqAp/WMHD46vsz6tkRNaNerVLCYAFeiRCTZeOtQc/xarPu6/v u/TjwMo8avi/ARYmuArKXkbyubSo69vC+40jLV3twPA6+BUk9oBmRNDj9lfLKW7alwdL 22RPNMv4/onNKZDx0I9gwbSPG6ea6wkQcpYPjVkZQGO2XAGmFa2PVtsRK7RDiRxFPasB PWxA== 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:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=jTLNKM1s6kTHfJCzBKKVyG04HCNYDjStSLVbGT2FnlI=; b=OED6Eq4s1LnY8Pck65NvTR7syyHfwyqoNHinaA50JwoSA26lL58QndrtDuIvjWo6LV UOm63yjf/4c31TCLzTkvergaMTLNtmD+SYjfqQemCy740GMHgjLdIODWwjuMQ8zelasR Xpx28hdrAEYTFzAP3zt59ZPBA0qdryXtdByAdgtOqkBm0aGGk1Jh4mMuEZ9D1X+jH7UE XAMx+DtHD5n9GxJxOwB3bONli/3yghDoBF/b5oHoMTeRhJdhABpRuHsQAsZ/1OduEPbE U4rnb7f06LsehGDMnIeLouPJjLNCvwkt687demOI6J67xOFNQK+FrXaEleKKtzol7g2u muKQ== 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 11-v6si6997667plb.383.2018.10.04.21.02.08; Thu, 04 Oct 2018 21:03:03 -0700 (PDT) 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 S1727532AbeJEK6w (ORCPT + 99 others); Fri, 5 Oct 2018 06:58:52 -0400 Received: from gate.crashing.org ([63.228.1.57]:44435 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726286AbeJEK6v (ORCPT ); Fri, 5 Oct 2018 06:58:51 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id w953PcSt004864; Thu, 4 Oct 2018 22:25:40 -0500 Message-ID: <8891277c7de92e93d3bfc409df95810ee6f103cd.camel@kernel.crashing.org> Subject: Re: [PATCH] memblock: stop using implicit alignement to SMP_CACHE_BYTES From: Benjamin Herrenschmidt To: Mike Rapoport , linux-mm@kvack.org Cc: linux-mips@linux-mips.org, Michal Hocko , linux-ia64@vger.kernel.org, Catalin Marinas , Richard Weinberger , Russell King , Ingo Molnar , Geert Uytterhoeven , Matt Turner , linux-um@lists.infradead.org, linux-m68k@vger.kernel.org, Thomas Gleixner , Guan Xuetao , linux-arm-kernel@lists.infradead.org, Chris Zankel , Michal Simek , Tony Luck , linux-kernel@vger.kernel.org, Paul Burton , linux-alpha@vger.kernel.org, Andrew Morton , linuxppc-dev@lists.ozlabs.org Date: Fri, 05 Oct 2018 13:25:38 +1000 In-Reply-To: <1538687224-17535-1-git-send-email-rppt@linux.vnet.ibm.com> References: <1538687224-17535-1-git-send-email-rppt@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-1.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2018-10-05 at 00:07 +0300, Mike Rapoport wrote: > When a memblock allocation APIs are called with align = 0, the alignment is > implicitly set to SMP_CACHE_BYTES. > > Replace all such uses of memblock APIs with the 'align' parameter explicitly > set to SMP_CACHE_BYTES and stop implicit alignment assignment in the > memblock internal allocation functions. > > For the case when memblock APIs are used via helper functions, e.g. like > iommu_arena_new_node() in Alpha, the helper functions were detected with > Coccinelle's help and then manually examined and updated where appropriate. > > The direct memblock APIs users were updated using the semantic patch below: What is the purpose of this ? It sounds rather counter-intuitive... Ben.