Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp801598ybg; Tue, 28 Jul 2020 20:35:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx9N+n3leCSiSNPYbQ4xRLf0z6zbuMGChfWWiExklGttKb2eLhjTAqmciRudHy3KvKyOrQb X-Received: by 2002:a50:e385:: with SMTP id b5mr28423077edm.130.1595993752042; Tue, 28 Jul 2020 20:35:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595993752; cv=none; d=google.com; s=arc-20160816; b=Tb6AruRb+4VHq3TPyY2o8tXDE/dEfluiDBZVFfd3+Ta2DUdW0F29iRui+l5/6W1PHq W+Y5OyAoY+TVTnrUEibilSN83eLsk03bZwkIOD1U1nOvq9CRXhlbDc3eENx4vB/FGLn6 /GvaQsD+o0sDlFk2bQq3AC23mZp4EXaLhm+vNWQ2DDttoSuOoOOdWCj/ygzefMGY1wxK +t79unT1hd0bvq4qTEMGexRhU1muw5XuDqNdGqZRarXBsFQCaJvUZNd8frKphgTO+o7f M12KW90/wmljgm0qR65GN52N2xrJIuzCLG/CCq8NLkJ6I+7jhY/VDvUbValNVF8brLJv FO9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=qCKFPyqSWdGG//q300Yrr0Owao5Aa4tsIDiSyfMXCP8=; b=jB/haY8Yuf4gk03ZI3E3H5tr8RHdgd3RGCnNolMmRYXdqAQe8gPGihRltOe/DHFnUx 6vOO2Dgqk/Q3/MIc5zfnXOFim97kNlLKphmXOKY81Ib2V8DvLkJX+nG0tVf2rDD+FM86 7tbMkmNFB/lfnBWLQn1cHLEqyM7k8Tw72QUOjVEEhoG1nPzDKv0DmVFalYn2BprofIal Ohf+NAoxiLxt/y4O4nk7hK9/LyaPuc6F8KMLpKbnNtzxFx0p+y9X2dDeFAYTA2dD5ZV5 dijBiazWt/UcoxddPSyr5v+Oku7Ya/VdMbnLp7k93bQLQj8CDVi9P6UuPYuCrmAMCjXC HGmw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c67si492861edf.421.2020.07.28.20.35.29; Tue, 28 Jul 2020 20:35:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726509AbgG2DfN (ORCPT + 99 others); Tue, 28 Jul 2020 23:35:13 -0400 Received: from foss.arm.com ([217.140.110.172]:44496 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726245AbgG2DfN (ORCPT ); Tue, 28 Jul 2020 23:35:13 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 309D631B; Tue, 28 Jul 2020 20:35:12 -0700 (PDT) Received: from localhost.localdomain (entos-thunderx2-02.shanghai.arm.com [10.169.212.213]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id A94CC3F66E; Tue, 28 Jul 2020 20:35:04 -0700 (PDT) From: Jia He To: Dan Williams , Vishal Verma , Mike Rapoport , David Hildenbrand Cc: Catalin Marinas , Will Deacon , Greg Kroah-Hartman , "Rafael J. Wysocki" , Dave Jiang , Andrew Morton , Steve Capper , Mark Rutland , Logan Gunthorpe , Anshuman Khandual , Hsin-Yi Wang , Jason Gunthorpe , Dave Hansen , Kees Cook , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-nvdimm@lists.01.org, linux-mm@kvack.org, Wei Yang , Pankaj Gupta , Ira Weiny , Kaly Xin , Jia He Subject: [RFC PATCH 0/6] decrease unnecessary gap due to pmem kmem alignment Date: Wed, 29 Jul 2020 11:34:18 +0800 Message-Id: <20200729033424.2629-1-justin.he@arm.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When enabling dax pmem as RAM device on arm64, I noticed that kmem_start addr in dev_dax_kmem_probe() should be aligned w/ SECTION_SIZE_BITS(30),i.e. 1G memblock size. Even Dan Williams' sub-section patch series [1] had been upstream merged, it was not helpful due to hard limitation of kmem_start: $ndctl create-namespace -e namespace0.0 --mode=devdax --map=dev -s 2g -f -a 2M $echo dax0.0 > /sys/bus/dax/drivers/device_dax/unbind $echo dax0.0 > /sys/bus/dax/drivers/kmem/new_id $cat /proc/iomem ... 23c000000-23fffffff : System RAM 23dd40000-23fecffff : reserved 23fed0000-23fffffff : reserved 240000000-33fdfffff : Persistent Memory 240000000-2403fffff : namespace0.0 280000000-2bfffffff : dax0.0 <- aligned with 1G boundary 280000000-2bfffffff : System RAM Hence there is a big gap between 0x2403fffff and 0x280000000 due to the 1G alignment. Without this series, if qemu creates a 4G bytes nvdimm device, we can only use 2G bytes for dax pmem(kmem) in the worst case. e.g. 240000000-33fdfffff : Persistent Memory We can only use the memblock between [240000000, 2ffffffff] due to the hard limitation. It wastes too much memory space. Decreasing the SECTION_SIZE_BITS on arm64 might be an alternative, but there are too many concerns from other constraints, e.g. PAGE_SIZE, hugetlb, SPARSEMEM_VMEMMAP, page bits in struct page ... Beside decreasing the SECTION_SIZE_BITS, we can also relax the kmem alignment with memory_block_size_bytes(). Tested on arm64 guest and x86 guest, qemu creates a 4G pmem device. dax pmem can be used as ram with smaller gap. Also the kmem hotplug add/remove are both tested on arm64/x86 guest. This patch series (mainly patch6/6) is based on the fixing patch, ~v5.8-rc5 [2]. [1] https://lkml.org/lkml/2019/6/19/67 [2] https://lkml.org/lkml/2020/7/8/1546 Jia He (6): mm/memory_hotplug: remove redundant memory block size alignment check resource: export find_next_iomem_res() helper mm/memory_hotplug: allow pmem kmem not to align with memory_block_size mm/page_alloc: adjust the start,end in dax pmem kmem case device-dax: relax the memblock size alignment for kmem_start arm64: fall back to vmemmap_populate_basepages if not aligned with PMD_SIZE arch/arm64/mm/mmu.c | 4 ++++ drivers/base/memory.c | 24 ++++++++++++++++-------- drivers/dax/kmem.c | 22 +++++++++++++--------- include/linux/ioport.h | 3 +++ kernel/resource.c | 3 ++- mm/memory_hotplug.c | 39 ++++++++++++++++++++++++++++++++++++++- mm/page_alloc.c | 14 ++++++++++++++ 7 files changed, 90 insertions(+), 19 deletions(-) -- 2.17.1