From patchwork Thu Aug 18 13:10:32 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Aneesh Kumar K.V" X-Patchwork-Id: 12948071 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89288C00140 for ; Thu, 18 Aug 2022 22:23:36 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1E38E8E0001; Thu, 18 Aug 2022 18:23:36 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 191F28D0002; Thu, 18 Aug 2022 18:23:36 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 05A108E0001; Thu, 18 Aug 2022 18:23:36 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id EC05A8D0002 for ; Thu, 18 Aug 2022 18:23:35 -0400 (EDT) Received: from smtpin07.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id C042D121A20 for ; Thu, 18 Aug 2022 22:23:35 +0000 (UTC) X-FDA: 79814141190.07.6BB5C96 Received: by imf03.hostedemail.com (Postfix, from userid 200) id 6883121BA7; Thu, 18 Aug 2022 15:54:35 +0000 (UTC) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by imf03.hostedemail.com (Postfix) with ESMTP id 81B1221437 for ; Thu, 18 Aug 2022 15:54:35 +0000 (UTC) Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 27ICC2aS006710; Thu, 18 Aug 2022 13:10:58 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=from : to : cc : subject : date : message-id : mime-version : content-transfer-encoding; s=pp1; bh=L5TWbRjfImzKrEffubUu44UbEic2E79aSms+3T/91u8=; b=Q1YIxUu0fkVCVBG2A2nzjGSV9WIhorYJYJMzK6wfEhvs0SIF9yB53R70rK9JsnOfAyUJ +aEV25v9/RTmLLSQuYnyBhj85mBVfKaHikaC91Mf9jg7AO4GuxK+7LdpnxueQgg3tbrU Xg5q8+4yraCbnQmNERZLb77ip87R5UKvDtI2YphFW4az9CAcTA6zuShagBkYUdjn6RX/ Vhiy375ns4BJm3W693C1MY4Pjh2YO3Oa70CF/2y5/ZfEZxWnUepuZXb8DSaYF8nFxcTf dxsOg8EsldEdk2zYTcx/Ta9w3DzhI6OaDAYx+tvuqoa7yx8gr9CPzW1wxR4mNHAYHaZJ 8g== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3j1n7cj4nx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Aug 2022 13:10:57 +0000 Received: from m0098409.ppops.net (m0098409.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 27ICDUW3012176; Thu, 18 Aug 2022 13:10:56 GMT Received: from ppma01wdc.us.ibm.com (fd.55.37a9.ip4.static.sl-reverse.com [169.55.85.253]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3j1n7cj4n3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Aug 2022 13:10:56 +0000 Received: from pps.filterd (ppma01wdc.us.ibm.com [127.0.0.1]) by ppma01wdc.us.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 27ID6VX7003245; Thu, 18 Aug 2022 13:10:55 GMT Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by ppma01wdc.us.ibm.com with ESMTP id 3hx3k9pyda-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 18 Aug 2022 13:10:55 +0000 Received: from b01ledav002.gho.pok.ibm.com (b01ledav002.gho.pok.ibm.com [9.57.199.107]) by b01cxnp22035.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 27IDAsGB3015388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 18 Aug 2022 13:10:54 GMT Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C8929124053; Thu, 18 Aug 2022 13:10:54 +0000 (GMT) Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D00A2124052; Thu, 18 Aug 2022 13:10:49 +0000 (GMT) Received: from skywalker.ibmuc.com (unknown [9.43.111.107]) by b01ledav002.gho.pok.ibm.com (Postfix) with ESMTP; Thu, 18 Aug 2022 13:10:49 +0000 (GMT) From: "Aneesh Kumar K.V" To: linux-mm@kvack.org, akpm@linux-foundation.org Cc: Wei Xu , Huang Ying , Yang Shi , Davidlohr Bueso , Tim C Chen , Michal Hocko , Linux Kernel Mailing List , Hesham Almatary , Dave Hansen , Jonathan Cameron , Alistair Popple , Dan Williams , Johannes Weiner , jvgediya.oss@gmail.com, Bharata B Rao , "Aneesh Kumar K.V" Subject: [PATCH v15 00/10] mm/demotion: Memory tiers and demotion Date: Thu, 18 Aug 2022 18:40:32 +0530 Message-Id: <20220818131042.113280-1-aneesh.kumar@linux.ibm.com> X-Mailer: git-send-email 2.37.2 MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-Proofpoint-GUID: Pm2csQK-EUBzD4TY3JJzYqWQTkZXcJeV X-Proofpoint-ORIG-GUID: xbfyysA_svCvPRaOawPVTgU7yK5euI4e X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-08-18_12,2022-08-18_01,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 adultscore=0 malwarescore=0 bulkscore=0 impostorscore=0 phishscore=0 priorityscore=1501 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxlogscore=999 suspectscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2207270000 definitions=main-2208180045 ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1660838075; a=rsa-sha256; cv=none; b=t05XETUHFzIOI/1V6c1xqUsz55Enex27TpUGpTMmR1NRSwfLKWEOzamgNcxpNvf75x52io /pge92f+5+p9z+UNvOOxkuGj4BNQIGpaxQgUlMGGFAWXQKHVkkxN9qsVd+MZ8/p5H3wJ21 jOP0n9KD0O2xELejgK0N4RMQIdSGX44= ARC-Authentication-Results: i=1; imf03.hostedemail.com; dkim=pass header.d=ibm.com header.s=pp1 header.b=Q1YIxUu0; dmarc=pass (policy=none) header.from=ibm.com; spf=pass (imf03.hostedemail.com: domain of aneesh.kumar@linux.ibm.com designates 148.163.156.1 as permitted sender) smtp.mailfrom=aneesh.kumar@linux.ibm.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1660838075; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-transfer-encoding:content-transfer-encoding: in-reply-to:references:dkim-signature; bh=L5TWbRjfImzKrEffubUu44UbEic2E79aSms+3T/91u8=; b=fS45gu7DK5dYdoC/xZvMSZYhif6NsJelBe3Bpfa4uIQ88MxbK8Gll5Lxog7BQS+6bROrtE 3QM0gq9JyTTJM8+ggcP8ZfqvOXHbP7rd+/JLtlNYJVyDT5TrXwHWtG+iSY3mlqezd3uchq udi7pQrEg/KrmOoaOwV8ZVdtqHLij9c= Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=ibm.com header.s=pp1 header.b=Q1YIxUu0; dmarc=pass (policy=none) header.from=ibm.com; spf=pass (imf03.hostedemail.com: domain of aneesh.kumar@linux.ibm.com designates 148.163.156.1 as permitted sender) smtp.mailfrom=aneesh.kumar@linux.ibm.com X-Rspam-User: X-Rspamd-Server: rspam07 X-Stat-Signature: e7uh4ctwytbfttt3whbg6dudyo7cp43g X-Rspamd-Queue-Id: 81B1221437 X-HE-Tag: 1660838075-274692 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: The current kernel has the basic memory tiering support: Inactive pages on a higher tier NUMA node can be migrated (demoted) to a lower tier NUMA node to make room for new allocations on the higher tier NUMA node. Frequently accessed pages on a lower tier NUMA node can be migrated (promoted) to a higher tier NUMA node to improve the performance. In the current kernel, memory tiers are defined implicitly via a demotion path relationship between NUMA nodes, which is created during the kernel initialization and updated when a NUMA node is hot-added or hot-removed. The current implementation puts all nodes with CPU into the highest tier, and builds the tier hierarchy tier-by-tier by establishing the per-node demotion targets based on the distances between nodes. This current memory tier kernel implementation needs to be improved for several important use cases: * The current tier initialization code always initializes each memory-only NUMA node into a lower tier. But a memory-only NUMA node may have a high performance memory device (e.g. a DRAM-backed memory-only node on a virtual machine) and that should be put into a higher tier. * The current tier hierarchy always puts CPU nodes into the top tier. But on a system with HBM (e.g. GPU memory) devices, these memory-only HBM NUMA nodes should be in the top tier, and DRAM nodes with CPUs are better to be placed into the next lower tier. * Also because the current tier hierarchy always puts CPU nodes into the top tier, when a CPU is hot-added (or hot-removed) and triggers a memory node from CPU-less into a CPU node (or vice versa), the memory tier hierarchy gets changed, even though no memory node is added or removed. This can make the tier hierarchy unstable and make it difficult to support tier-based memory accounting. * A higher tier node can only be demoted to nodes with shortest distance on the next lower tier as defined by the demotion path, not any other node from any lower tier. This strict, demotion order does not work in all use cases (e.g. some use cases may want to allow cross-socket demotion to another node in the same demotion tier as a fallback when the preferred demotion node is out of space), and has resulted in the feature request for an interface to override the system-wide, per-node demotion order from the userspace. This demotion order is also inconsistent with the page allocation fallback order when all the nodes in a higher tier are out of space: The page allocation can fall back to any node from any lower tier, whereas the demotion order doesn't allow that. This patch series make the creation of memory tiers explicit under the control of device driver. Memory Tier Initialization ========================== Linux kernel presents memory devices as NUMA nodes and each memory device is of a specific type. The memory type of a device is represented by its abstract distance. A memory tier corresponds to a range of abstract distance. This allows for classifying memory devices with a specific performance range into a memory tier. By default, all memory nodes are assigned to the default tier with abstract distance 512. A device driver can move its memory nodes from the default tier. For example, PMEM can move its memory nodes below the default tier, whereas GPU can move its memory nodes above the default tier. The kernel initialization code makes the decision on which exact tier a memory node should be assigned to based on the requests from the device drivers as well as the memory device hardware information provided by the firmware. Hot-adding/removing CPUs doesn't affect memory tier hierarchy. Changes from v14 * Add Reviewed-by: * Address review feedback w.r.t default adistance value Changes from v13 * Address review feedback. * Add path dropping memtier from struct memory_dev_type Changes from v12 * Fix kernel crash on module unload * Address review feedback. * Add node_random patch to this series based on review feedback Changes from v11: * smaller abstract distance imply faster(higher) memory tier. Changes from v10: * rename performance level to abstract distance * Thanks to all the good feedback from Huang, Ying . Updated the patchset to cover most of the review feedback. Changes from v9: * Use performance level for initializing memory tiers. Changes from v8: * Drop the sysfs interface patches and related documentation changes. Changes from v7: * Fix kernel crash with demotion. * Improve documentation. Changes from v6: * Drop the usage of rank. * Address other review feedback. Changes from v5: * Remove patch supporting N_MEMORY node removal from memory tiers. memory tiers are going to be used for features other than demotion. Hence keep all N_MEMORY nodes in memory tiers irrespective of whether they want to participate in promotion or demotion. * Add NODE_DATA->memtier * Rearrage patches to add sysfs files later. * Add support to create memory tiers from userspace. * Address other review feedback. Changes from v4: * Address review feedback. * Reverse the meaning of "rank": higher rank value means higher tier. * Add "/sys/devices/system/memtier/default_tier". * Add node_is_toptier v4: Add support for explicit memory tiers and ranks. v3: - Modify patch 1 subject to make it more specific - Remove /sys/kernel/mm/numa/demotion_targets interface, use /sys/devices/system/node/demotion_targets instead and make it writable to override node_states[N_DEMOTION_TARGETS]. - Add support to view per node demotion targets via sysfs v2: In v1, only 1st patch of this patch series was sent, which was implemented to avoid some of the limitations on the demotion target sharing, however for certain numa topology, the demotion targets found by that patch was not most optimal, so 1st patch in this series is modified according to suggestions from Huang and Baolin. Different examples of demotion list comparasion between existing implementation and changed implementation can be found in the commit message of 1st patch. Aneesh Kumar K.V (9): mm/demotion: Add support for explicit memory tiers mm/demotion: Move memory demotion related code mm/demotion: Add hotplug callbacks to handle new numa node onlined mm/demotion/dax/kmem: Set node's abstract distance to MEMTIER_DEFAULT_DAX_ADISTANCE mm/demotion: Build demotion targets based on explicit memory tiers mm/demotion: Add pg_data_t member to track node memory tier details mm/demotion: Drop memtier from memtype mm/demotion: Update node_is_toptier to work with memory tiers lib/nodemask: Optimize node_random for nodemask with single NUMA node Jagdish Gediya (1): mm/demotion: Demote pages according to allocation fallback order drivers/dax/kmem.c | 42 ++- include/linux/memory-tiers.h | 102 ++++++ include/linux/migrate.h | 15 - include/linux/mmzone.h | 3 + include/linux/node.h | 5 - include/linux/nodemask.h | 15 +- mm/Makefile | 1 + mm/huge_memory.c | 1 + mm/memory-tiers.c | 645 +++++++++++++++++++++++++++++++++++ mm/migrate.c | 453 +----------------------- mm/mprotect.c | 1 + mm/vmscan.c | 59 +++- mm/vmstat.c | 4 - 13 files changed, 849 insertions(+), 497 deletions(-) create mode 100644 include/linux/memory-tiers.h create mode 100644 mm/memory-tiers.c Acked-by: Wei Xu