From patchwork Thu Mar 11 08:18:15 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Huang, Ying" X-Patchwork-Id: 12130587 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-16.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 94E5AC433E0 for ; Thu, 11 Mar 2021 08:19:16 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 1828264E22 for ; Thu, 11 Mar 2021 08:19:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1828264E22 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 76EC48D0280; Thu, 11 Mar 2021 03:19:15 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 71E8A8D0250; Thu, 11 Mar 2021 03:19:15 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 60CFA8D0280; Thu, 11 Mar 2021 03:19:15 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 48A9B8D0250 for ; Thu, 11 Mar 2021 03:19:15 -0500 (EST) Received: from smtpin26.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 0941D181AF5C4 for ; Thu, 11 Mar 2021 08:19:15 +0000 (UTC) X-FDA: 77906893470.26.41BB3B8 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by imf16.hostedemail.com (Postfix) with ESMTP id AD0F18019141 for ; Thu, 11 Mar 2021 08:19:12 +0000 (UTC) IronPort-SDR: Xp5LtvZ2LVMy+aSvGwey/7UfX4IKNWurg1v7fjjDtyRYFRfP1yGoleI51tj7hormGaz+/69Ulj 3PEtwkEziFcQ== X-IronPort-AV: E=McAfee;i="6000,8403,9919"; a="186253529" X-IronPort-AV: E=Sophos;i="5.81,239,1610438400"; d="scan'208";a="186253529" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Mar 2021 00:19:10 -0800 IronPort-SDR: /2g2KcpmZ52Dw/TqC3r3vMRY+meoH0EDa8MsyRDhH+9vy903uhzhQNVQkUa6RuNqoqeTqb2qaS nLipLKF0/ywA== X-IronPort-AV: E=Sophos;i="5.81,239,1610438400"; d="scan'208";a="410527508" Received: from yhuang6-mobl1.sh.intel.com ([10.238.6.89]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Mar 2021 00:19:06 -0800 From: Huang Ying To: Peter Zijlstra Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Huang Ying , Andrew Morton , Michal Hocko , Rik van Riel , Mel Gorman , Ingo Molnar , Dave Hansen , Dan Williams Subject: [RFC -V6 0/6] NUMA balancing: optimize memory placement for memory tiering system Date: Thu, 11 Mar 2021 16:18:15 +0800 Message-Id: <20210311081821.138467-1-ying.huang@intel.com> X-Mailer: git-send-email 2.30.1 MIME-Version: 1.0 X-Stat-Signature: s791kkt1hzkkgah9e1imrrn668mjo5r6 X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: AD0F18019141 Received-SPF: none (intel.com>: No applicable sender policy available) receiver=imf16; identity=mailfrom; envelope-from=""; helo=mga04.intel.com; client-ip=192.55.52.120 X-HE-DKIM-Result: none/none X-HE-Tag: 1615450752-160924 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: With the advent of various new memory types, some machines will have multiple types of memory, e.g. DRAM and PMEM (persistent memory). The memory subsystem of these machines can be called memory tiering system, because the performance of the different types of memory are usually different. After commit c221c0b0308f ("device-dax: "Hotplug" persistent memory for use like normal RAM"), the PMEM could be used as the cost-effective volatile memory in separate NUMA nodes. In a typical memory tiering system, there are CPUs, DRAM and PMEM in each physical NUMA node. The CPUs and the DRAM will be put in one logical node, while the PMEM will be put in another (faked) logical node. To optimize the system overall performance, the hot pages should be placed in DRAM node. To do that, we need to identify the hot pages in the PMEM node and migrate them to DRAM node via NUMA migration. In the original NUMA balancing, there are already a set of existing mechanisms to identify the pages recently accessed by the CPUs in a node and migrate the pages to the node. So we can reuse these mechanisms to build the mechanisms to optimize the page placement in the memory tiering system. This has been implemented in this patchset. At the other hand, the cold pages should be placed in PMEM node. So, we also need to identify the cold pages in the DRAM node and migrate them to PMEM node. In the following patchset, [PATCH 00/10] [v6] Migrate Pages in lieu of discard https://lore.kernel.org/lkml/20210304235949.7922C1C3@viggo.jf.intel.com/ A mechanism to demote the cold DRAM pages to PMEM node under memory pressure is implemented. Based on that, the cold DRAM pages can be demoted to PMEM node proactively to free some memory space on DRAM node. And this frees the space on DRAM node for the hot PMEM pages to be promoted to. This has been implemented in this patchset too. The patchset is based on the following not-yet-merged patchset, [PATCH 00/10] [v6] Migrate Pages in lieu of discard https://lore.kernel.org/lkml/20210304235949.7922C1C3@viggo.jf.intel.com/ This is part of a larger patch set. If you want to apply these or play with them, I'd suggest using the tree from below, https://github.com/hying-caritas/linux/commits/autonuma-r6 We have tested the solution with the pmbench memory accessing benchmark with the 80:20 read/write ratio and the normal access address distribution on a 2 socket Intel server with Optane DC Persistent Memory Model. The test results of the base kernel and step by step optimizations are as follows, Throughput Promotion DRAM bandwidth access/s MB/s MB/s ----------- ---------- -------------- Base 74238178.0 4291.7 Patch 2 146050652.3 359.4 11248.6 Patch 3 146300787.1 355.2 11237.2 Patch 4 162536383.0 211.7 11890.4 Patch 5 157187775.0 105.9 10412.3 Patch 6 164028415.2 73.3 10810.6 The whole patchset improves the benchmark score up to 119.1%. The basic NUMA balancing based optimization solution (patch 1), the hot page selection algorithm (patch 4), and the threshold automatic adjustment algorithms (patch 6) improves the performance or reduce the overhead (promotion MB/s) mostly. Changelog: v6: - Rebased on the latest page demotion patchset. (which bases on v5.11) v5: - Rebased on the latest page demotion patchset. (which bases on v5.10) v4: - Rebased on the latest page demotion patchset. (which bases on v5.9-rc6) - Add page promotion counter. v3: - Move the rate limit control as late as possible per Mel Gorman's comments. - Revise the hot page selection implementation to store page scan time in struct page. - Code cleanup. - Rebased on the latest page demotion patchset. v2: - Addressed comments for V1. - Rebased on v5.5. Huang Ying (6): NUMA balancing: optimize page placement for memory tiering system memory tiering: add page promotion counter memory tiering: skip to scan fast memory memory tiering: hot page selection with hint page fault latency memory tiering: rate limit NUMA migration throughput memory tiering: adjust hot threshold automatically include/linux/mm.h | 29 ++++++++ include/linux/mmzone.h | 11 ++++ include/linux/node.h | 5 ++ include/linux/sched/sysctl.h | 12 ++++ kernel/sched/core.c | 9 +-- kernel/sched/fair.c | 124 +++++++++++++++++++++++++++++++++++ kernel/sysctl.c | 22 ++++++- mm/huge_memory.c | 41 ++++++++---- mm/memory.c | 11 +++- mm/migrate.c | 52 +++++++++++++-- mm/mmzone.c | 17 +++++ mm/mprotect.c | 19 +++++- mm/vmscan.c | 15 +++++ mm/vmstat.c | 4 ++ 14 files changed, 345 insertions(+), 26 deletions(-) Best Regards, Huang, Ying