Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp3841558imd; Mon, 29 Oct 2018 13:15:01 -0700 (PDT) X-Google-Smtp-Source: AJdET5cxJ1bxjO4RJAVJ/sT96mNqCfLkQQWjyqceFKU6J2ikkM9TVYSpDl0nZqysOrAnT28nxUiK X-Received: by 2002:a63:d705:: with SMTP id d5-v6mr15033939pgg.27.1540844101899; Mon, 29 Oct 2018 13:15:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540844101; cv=none; d=google.com; s=arc-20160816; b=FfVWafhLuy45tCLe+QwtjPmLs9exsbR5oUaNSzqZ8XVvynb7Ujm4UBeHCAbZMmZCT+ T01rpSYdQNAu8oEue6pTEA3xS/F8DGL53VAUmGTWM3lIKldOV5klMlTZeDfhmz5DVvCj q3R8/BLkhhKipCBkbxoj0OY/S7V98Y55531TcSQdtm8fCdharzhsoY6TP1SJvI8WH+Po PEriKnmeFhtvpjT9LPm1aiQmBuqjU3Hrbr5ViPPa2gBGrl/rKVk+veRMRb/37zHMleOK 7AvClwa0d0yTJvhXa8k/aYgBEX40M6opASwc0WTXZPpRCc5tGB+AxhO9l32z1Jl/XTDi EvJA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=j/7pjEEz6yl2QLHFKhrNfRj8JBOwQp7dLpdm+xE9bUQ=; b=W0cn+IlBT8MpNER1x720BlUhQgwxwqmkR4rgDWSyXpz4J4RtepJVfrXaPnLCyvZ314 j4q2fKFjPmkJljdXsR72zKeBqZsMp/kgvD+RAkavOKreWwL/O2iC1RVgb2cgZX1c6UoX wbnwmHqG2ewLkRWB2y9EjthzrVvZn0qlFVlmjhoGWoiMqjDdRHxj8tD8LEjB+5J7Gfj3 QvHVSaLvw2b2CrlMpnkENxqcpgI3vbNMv2JljHADeZjArmb6ISekVhE3lgkDyfJR1FE1 RskkCuvwMGledPkN0hwOQ3G33M2SUQRJ03s6d9FHyMH45r+QpjLOj1fD0T6O+y2EHK67 +cfg== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d19-v6si8206812pgg.227.2018.10.29.13.14.46; Mon, 29 Oct 2018 13:15:01 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729671AbeJ3FCi (ORCPT + 99 others); Tue, 30 Oct 2018 01:02:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:46036 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726034AbeJ3FCi (ORCPT ); Tue, 30 Oct 2018 01:02:38 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C22DBAC8D; Mon, 29 Oct 2018 20:12:22 +0000 (UTC) Date: Mon, 29 Oct 2018 21:12:21 +0100 From: Michal Hocko To: Alexander Duyck Cc: linux-mm@kvack.org, akpm@linux-foundation.org, pavel.tatashin@microsoft.com, dave.jiang@intel.com, linux-kernel@vger.kernel.org, willy@infradead.org, davem@davemloft.net, yi.z.zhang@linux.intel.com, khalid.aziz@oracle.com, rppt@linux.vnet.ibm.com, vbabka@suse.cz, sparclinux@vger.kernel.org, dan.j.williams@intel.com, ldufour@linux.vnet.ibm.com, mgorman@techsingularity.net, mingo@kernel.org, kirill.shutemov@linux.intel.com Subject: Re: [mm PATCH v4 1/6] mm: Use mm_zero_struct_page from SPARC on all 64b architectures Message-ID: <20181029201221.GP32673@dhcp22.suse.cz> References: <20181017235043.17213.92459.stgit@localhost.localdomain> <20181017235408.17213.38641.stgit@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181017235408.17213.38641.stgit@localhost.localdomain> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 17-10-18 16:54:08, Alexander Duyck wrote: > This change makes it so that we use the same approach that was already in > use on Sparc on all the archtectures that support a 64b long. > > This is mostly motivated by the fact that 7 to 10 store/move instructions > are likely always going to be faster than having to call into a function > that is not specialized for handling page init. > > An added advantage to doing it this way is that the compiler can get away > with combining writes in the __init_single_page call. As a result the > memset call will be reduced to only about 4 write operations, or at least > that is what I am seeing with GCC 6.2 as the flags, LRU poitners, and > count/mapcount seem to be cancelling out at least 4 of the 8 assignments on > my system. > > One change I had to make to the function was to reduce the minimum page > size to 56 to support some powerpc64 configurations. > > This change should introduce no change on SPARC since it already had this > code. In the case of x86_64 I saw a reduction from 3.75s to 2.80s when > initializing 384GB of RAM per node. Pavel Tatashin tested on a system with > Broadcom's Stingray CPU and 48GB of RAM and found that __init_single_page() > takes 19.30ns / 64-byte struct page before this patch and with this patch > it takes 17.33ns / 64-byte struct page. Mike Rapoport ran a similar test on > a OpenPower (S812LC 8348-21C) with Power8 processor and 128GB or RAM. His > results per 64-byte struct page were 4.68ns before, and 4.59ns after this > patch. > > Signed-off-by: Alexander Duyck I thought I have sent my ack already but haven't obviously. Acked-by: Michal Hocko Thanks for the updated version. I will try to get to the rest of the series soon. > --- > arch/sparc/include/asm/pgtable_64.h | 30 -------------------------- > include/linux/mm.h | 41 ++++++++++++++++++++++++++++++++--- > 2 files changed, 38 insertions(+), 33 deletions(-) > > diff --git a/arch/sparc/include/asm/pgtable_64.h b/arch/sparc/include/asm/pgtable_64.h > index 1393a8ac596b..22500c3be7a9 100644 > --- a/arch/sparc/include/asm/pgtable_64.h > +++ b/arch/sparc/include/asm/pgtable_64.h > @@ -231,36 +231,6 @@ > extern struct page *mem_map_zero; > #define ZERO_PAGE(vaddr) (mem_map_zero) > > -/* This macro must be updated when the size of struct page grows above 80 > - * or reduces below 64. > - * The idea that compiler optimizes out switch() statement, and only > - * leaves clrx instructions > - */ > -#define mm_zero_struct_page(pp) do { \ > - unsigned long *_pp = (void *)(pp); \ > - \ > - /* Check that struct page is either 64, 72, or 80 bytes */ \ > - BUILD_BUG_ON(sizeof(struct page) & 7); \ > - BUILD_BUG_ON(sizeof(struct page) < 64); \ > - BUILD_BUG_ON(sizeof(struct page) > 80); \ > - \ > - switch (sizeof(struct page)) { \ > - case 80: \ > - _pp[9] = 0; /* fallthrough */ \ > - case 72: \ > - _pp[8] = 0; /* fallthrough */ \ > - default: \ > - _pp[7] = 0; \ > - _pp[6] = 0; \ > - _pp[5] = 0; \ > - _pp[4] = 0; \ > - _pp[3] = 0; \ > - _pp[2] = 0; \ > - _pp[1] = 0; \ > - _pp[0] = 0; \ > - } \ > -} while (0) > - > /* PFNs are real physical page numbers. However, mem_map only begins to record > * per-page information starting at pfn_base. This is to handle systems where > * the first physical page in the machine is at some huge physical address, > diff --git a/include/linux/mm.h b/include/linux/mm.h > index fcf9cc9d535f..6e2c9631af05 100644 > --- a/include/linux/mm.h > +++ b/include/linux/mm.h > @@ -98,10 +98,45 @@ static inline void set_max_mapnr(unsigned long limit) { } > > /* > * On some architectures it is expensive to call memset() for small sizes. > - * Those architectures should provide their own implementation of "struct page" > - * zeroing by defining this macro in . > + * If an architecture decides to implement their own version of > + * mm_zero_struct_page they should wrap the defines below in a #ifndef and > + * define their own version of this macro in > */ > -#ifndef mm_zero_struct_page > +#if BITS_PER_LONG == 64 > +/* This function must be updated when the size of struct page grows above 80 > + * or reduces below 56. The idea that compiler optimizes out switch() > + * statement, and only leaves move/store instructions. Also the compiler can > + * combine write statments if they are both assignments and can be reordered, > + * this can result in several of the writes here being dropped. > + */ > +#define mm_zero_struct_page(pp) __mm_zero_struct_page(pp) > +static inline void __mm_zero_struct_page(struct page *page) > +{ > + unsigned long *_pp = (void *)page; > + > + /* Check that struct page is either 56, 64, 72, or 80 bytes */ > + BUILD_BUG_ON(sizeof(struct page) & 7); > + BUILD_BUG_ON(sizeof(struct page) < 56); > + BUILD_BUG_ON(sizeof(struct page) > 80); > + > + switch (sizeof(struct page)) { > + case 80: > + _pp[9] = 0; /* fallthrough */ > + case 72: > + _pp[8] = 0; /* fallthrough */ > + case 64: > + _pp[7] = 0; /* fallthrough */ > + case 56: > + _pp[6] = 0; > + _pp[5] = 0; > + _pp[4] = 0; > + _pp[3] = 0; > + _pp[2] = 0; > + _pp[1] = 0; > + _pp[0] = 0; > + } > +} > +#else > #define mm_zero_struct_page(pp) ((void)memset((pp), 0, sizeof(struct page))) > #endif > > -- Michal Hocko SUSE Labs