From patchwork Sun Jan 1 09:45:22 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Mike Rapoport X-Patchwork-Id: 37943 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4e01:0:0:0:0:0 with SMTP id p1csp3701492wrt; Sun, 1 Jan 2023 01:47:04 -0800 (PST) X-Google-Smtp-Source: AMrXdXuBS7FRRYGs8Q6nooUl0iBMtdS5Ax/I1UrzqJmwP0YNwZAA41FUcoPk8Vnkkud/9rrh2r7T X-Received: by 2002:a05:6402:2296:b0:468:354a:4d6 with SMTP id cw22-20020a056402229600b00468354a04d6mr29900850edb.20.1672566424076; Sun, 01 Jan 2023 01:47:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672566424; cv=none; d=google.com; s=arc-20160816; b=qKu8vLlxFdoHBTk3NCyO5cdlg+AqEYs25wWqD/UAdBPE3bUFcu99tc7zZDrFkC0PNA tFdZou7bDwo5RyZbLBrTDNi8K+zqOZi9DpVIJqz7wbY5r+fPldhJl02Oq3CSHd847l4H 8d43lRLrY8Dzpw4jL5VXz6XReCiClqzY3EfLv83TUHPyUnaoC0ARTiuLq4nkeS8S79SM OB+ySXXT+yJtEIWZDzHI6Bs2bL4E1H7GT2S6kgOPFwSSvOoCqxO3Sb/uI8s+sQldzQxP nL7TZs2tRxacws7DcaPpoEgjI4Z29+yelHDdATCvRN1cKvd/J6+cSON1DqvWWjpLx/9N 0P1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=GeMxW6/bo7t8CedbH0ljza4tMQodK6qFd732yujZOBQ=; b=UxiKg204cC9RymCirKBnOUDeKzhrvq/AFrfX7bHV729Hqfwk6IVeRiLhLfvxWPegOe LufDlBmeJt2Ck9mztQCGefRYW6bTqLh6vCaJgBXGpYtPk2qUdvXwxIgrxbUiAm1lrTU5 jA/IP4uTQTzQLU/Qzuj/8S+gW6mKdgF8kn50gHiVqDtDgE7PUaQO6Va44NEd6rCM4hQx R/LI5CGA+E7fxbZ6OOWMBaStxhz+b/AE4I0ops5cHWoLnw6c4EwnVgux0eZ5eASGonWF fIvpgvoLw7+aaEjxr7QtUuDCwUHnPOV2y7VfmD4usUfB2T73Crmm7t+iTf5HdBpLyjzI rwVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=LSwwzypn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id dz8-20020a0564021d4800b0046b998ac55bsi25924438edb.575.2023.01.01.01.46.40; Sun, 01 Jan 2023 01:47:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=LSwwzypn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229729AbjAAJpp (ORCPT + 99 others); Sun, 1 Jan 2023 04:45:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229631AbjAAJpm (ORCPT ); Sun, 1 Jan 2023 04:45:42 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E5A2238B7; Sun, 1 Jan 2023 01:45:41 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6FE3860D3D; Sun, 1 Jan 2023 09:45:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 82D4AC433F0; Sun, 1 Jan 2023 09:45:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1672566340; bh=ZLGBlhqw5hH+SxGqvaz0vux+DdR7ulM6iEJUTeGEBI0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=LSwwzypnpxZ3H85D2YBEdZVPE/TRDKRP3ryXydYoZefESGnt6H7OCoiHhlCv76bTW WNsDwPgC2L39QzADbYxOUtZ5vf8ia3V9oTIiY7BB0vnSPuWFhY7jC39amHSpkjl9qZ RnqpefIgXHJkGnQ1HoqbDXd331YBoJFJiUklCqIbOf5rn5IbhXkBJ+3w+zLmlvodBn jTk9oK8pN9j1brqpgBsL/YkXwVd+D9XQyRRvDztUu5lG0D+pTEMEkceTPHysQ+6szl 0WGgLxEBeq+937o1Ve2rDdsaqu8Ek9mJGTcCzJ1tK358+nYc9YyGg7PqyOmpi4lPZ9 BBxKhRagu/abQ== From: Mike Rapoport To: Jonathan Corbet Cc: Andrew Morton , David Hildenbrand , Johannes Weiner , Lorenzo Stoakes , "Matthew Wilcox (Oracle)" , Mel Gorman , Michal Hocko , Mike Rapoport , Vlastimil Babka , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH 1/2] docs/mm: Page Reclaim: add page label to allow external references Date: Sun, 1 Jan 2023 11:45:22 +0200 Message-Id: <20230101094523.1522109-2-rppt@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20230101094523.1522109-1-rppt@kernel.org> References: <20230101094523.1522109-1-rppt@kernel.org> MIME-Version: 1.0 X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1753813010387433632?= X-GMAIL-MSGID: =?utf-8?q?1753813010387433632?= From: "Mike Rapoport (IBM)" Signed-off-by: Mike Rapoport (IBM) --- Documentation/mm/page_reclaim.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/mm/page_reclaim.rst b/Documentation/mm/page_reclaim.rst index 50a30b7f8ac3..3fccde066436 100644 --- a/Documentation/mm/page_reclaim.rst +++ b/Documentation/mm/page_reclaim.rst @@ -1,5 +1,7 @@ .. SPDX-License-Identifier: GPL-2.0 +.. _page_reclaim: + ============ Page Reclaim ============ From patchwork Sun Jan 1 09:45:23 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Mike Rapoport X-Patchwork-Id: 37944 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4e01:0:0:0:0:0 with SMTP id p1csp3701964wrt; Sun, 1 Jan 2023 01:49:28 -0800 (PST) X-Google-Smtp-Source: AMrXdXuCUuk7AFaxD64PXCSoxHO0pwc9INDKOgi6poCKDTgedDX7mApmL7YOIhiwTr4t4bE2fmzK X-Received: by 2002:a17:90a:e392:b0:219:f9d9:c82e with SMTP id b18-20020a17090ae39200b00219f9d9c82emr41417447pjz.42.1672566567720; Sun, 01 Jan 2023 01:49:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672566567; cv=none; d=google.com; s=arc-20160816; b=iuIxggPFbdSrli2bpQxmSLDlXNEUUNTfZsECa3jA+Jaw3OdXLCgA1RuyBSb8jxlWPV Cw500TpFtmqHC8GiJb8xwJ9JotJyA6BnhGpW+u4Fe/D/IYObzmX66pzuEzLG/mlnykTz PfxxyenF8PNlMOa/0BpohbjjNkzS+YT1tzwJ0so4kBNQu2giiNcSkm0qjkFSPVMpJ6rg AQCh2VSYl2xMcsLfBErwcDtGgiZdjCTVQ9Ib0iuxief08bYYc/zRxIommJwrQLxfQyJx 9mkyMm00MJUR7V5KgwQBDJvSArm+6d5uijPAr7yU+Vz8SKoTp1ABIivP10Ewtgrrkp9+ icHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=asXBjPSqL7evS2C0knrDSO1jJoTzWxHdCyo0efJjigo=; b=NNYU9Q0ptPcQE3hvHVKEaHg7o9e5JAOtVH5RVr8sAL/lCLjzQw9fIWRxNXwdH6+xrY 94ducKaklv++8/WlQgiFQ5+c3oqZ/PFe+mR+ditfpmfL/RiqKcBz1QI45h7VFETl/rtN JQhFNE6EztbISUczRHer4knPeUfpV9a9bqwFl+ATO9Z04QVWeBtE7G8kVemQftneAOYm WmTPasJ6YP8igOnnjDGk9Y6HYWWXpE+EFZaF1xEAH7QscQGRTTl78VEpr6LgJtHtpb9z XRTFDBa+EEmEdaT1Qh9IH8AuCaKRbsZ7Y7M/X78/cSpN2VhVz9+4ktVa787WQDxsb272 wOlg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=miH+Hc20; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e126-20020a636984000000b0047712cb3fe3si9426409pgc.590.2023.01.01.01.49.15; Sun, 01 Jan 2023 01:49:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=miH+Hc20; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230090AbjAAJpw (ORCPT + 99 others); Sun, 1 Jan 2023 04:45:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48302 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229781AbjAAJpr (ORCPT ); Sun, 1 Jan 2023 04:45:47 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E48B010F3; Sun, 1 Jan 2023 01:45:45 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 72D5760DB5; Sun, 1 Jan 2023 09:45:45 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5E3E4C433EF; Sun, 1 Jan 2023 09:45:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1672566344; bh=z9ZwLSxEOQtQ4Tc0WdCONTBI1jDHqtWw3QNCo6jVUzo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=miH+Hc20PPolZmCQ2J/uZ75viTP9KDzs1oLdt/pGRcUGzJykZLwj4t5sL6Z04nnFy uMa37kQwe/2Z7mCHfg3n4QByXMf8xkHAYWpVGH3qPKW2uAxpT15WuZQH9ivGpcktCG xRaW//DXutO/6t1HWXrAEO2auMgGoIjr2vWCFYvcgp5cCTmuhtA/tqWKV3ZGgKEzPV afB2mnk8tC5hTTePaW7Td+YrvHVK+UFuGCYp0DNX4pC2EY/ztnV1H2xt9jmxbPYGjS OLd+gGr1XDj6235aFJrynf9vbWtnldM6Qbu5OKATWciK1fjIeBDY/6NBYPN6OhjGAo E12pBydo9mtHg== From: Mike Rapoport To: Jonathan Corbet Cc: Andrew Morton , David Hildenbrand , Johannes Weiner , Lorenzo Stoakes , "Matthew Wilcox (Oracle)" , Mel Gorman , Michal Hocko , Mike Rapoport , Vlastimil Babka , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH 2/2] docs/mm: Physical Memory: add structure, introduction and nodes description Date: Sun, 1 Jan 2023 11:45:23 +0200 Message-Id: <20230101094523.1522109-3-rppt@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20230101094523.1522109-1-rppt@kernel.org> References: <20230101094523.1522109-1-rppt@kernel.org> MIME-Version: 1.0 X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1753813161135555363?= X-GMAIL-MSGID: =?utf-8?q?1753813161135555363?= From: "Mike Rapoport (IBM)" Signed-off-by: Mike Rapoport (IBM) --- Documentation/mm/physical_memory.rst | 322 +++++++++++++++++++++++++++ 1 file changed, 322 insertions(+) diff --git a/Documentation/mm/physical_memory.rst b/Documentation/mm/physical_memory.rst index 2ab7b8c1c863..fcf52f1db16b 100644 --- a/Documentation/mm/physical_memory.rst +++ b/Documentation/mm/physical_memory.rst @@ -3,3 +3,325 @@ =============== Physical Memory =============== + +Linux is available for a wide range of architectures so there is a need for an +architecture-independent abstraction to represent the physical memory. This +chapter describes the structures used to manage physical memory in a running +system. + +The first principal concept prevalent in the memory management is +`Non-Uniform Memory Access (NUMA) +`_. +With multi-core and multi-socket machines, memory may be arranged into banks +that incur a different cost to access depending on the “distance” from the +processor. For example, there might be a bank of memory assigned to each CPU or +a bank of memory very suitable for DMA near peripheral devices. + +Each bank is called a node and the concept is represented under Linux by a +``struct pglist_data`` even if the architecture is UMA. This structure is +always referenced to by it's typedef ``pg_data_t``. A pg_data_t structure +for a particular node can be referenced by ``NODE_DATA(nid)`` macro where +``nid`` is the ID of that node. + +For NUMA architectures, the node structures are allocated by the architecture +specific code early during boot. Usually, these structures are allocated +locally on the memory bank they represent. For UMA architectures, only one +static pg_data_t structure called ``contig_page_data`` is used. Nodes will +be discussed further in Section :ref:`Nodes ` + +Each node may be divided up into a number of blocks called zones which +represent ranges within memory. These ranges are usually determined by +architectural constraints for accessing the physical memory. A zone is +described by a ``struct zone_struct``, typedeffed to ``zone_t`` and each zone +has one of the types described below. + +`ZONE_DMA` and `ZONE_DMA32` + represent memory suitable for DMA by peripheral devices that cannot + access all of the addressable memory. Depending on the architecture, + either of these zone types or even they both can be disabled at build + time using ``CONFIG_ZONE_DMA`` and ``CONFIG_ZONE_DMA32`` configuration + options. Some 64-bit platforms may need both zones as they support + peripherals with different DMA addressing limitations. + +`ZONE_NORMAL` + is for normal memory that can be accessed by the kernel all the time. DMA + operations can be performed on pages in this zone if the DMA devices support + transfers to all addressable memory. ZONE_NORMAL is always enabled. + +`ZONE_HIGHMEM` + is the part of the physical memory that is not covered by a permanent mapping + in the kernel page tables. The memory in this zone is only accessible to the + kernel using temporary mappings. This zone is available only some 32-bit + architectures and is enabled with ``CONFIG_HIGHMEM``. + +`ZONE_MOVABLE` + is for normal accessible memory, just like ZONE_NORMAL. The difference is + that most pages in ZONE_MOVABLE are movable. That means that while virtual + addresses of these pages do not change, their content may move between + different physical pages. ZONE_MOVABLE is only enabled when one of + `kernelcore`, `movablecore` and `movable_node` parameters is present in the + kernel command line. See :ref:`Page migration ` for + additional details. + +`ZONE_DEVICE` + represents memory residing on devices such as PMEM and GPU. It has different + characteristics than RAM zone types and it exists to provide :ref:`struct + page ` and memory map services for device driver identified physical + address ranges. ZONE_DEVICE is enabled with configuration option + ``CONFIG_ZONE_DEVICE``. + +It is important to note that many kernel operations can only take place using +ZONE_NORMAL so it is the most performance critical zone. Zones are discussed +further in Section :ref:`Zones `. + +The relation between node and zone extents is determined by the physical memory +map reported by the firmware, architectural constraints for memory addressing +and certain parameters in the kernel command line. + +For example, with 32-bit kernel on an x86 UMA machine with 2 Gbytes of RAM the +entire memory will be on node 0 and there will be three zones: ZONE_DMA, +ZONE_NORMAL and ZONE_HIGHMEM:: + + 0 2G + +-------------------------------------------------------------+ + | node 0 | + +-------------------------------------------------------------+ + + 0 16M 896M 2G + +----------+-----------------------+--------------------------+ + | ZONE_DMA | ZONE_NORMAL | ZONE_HIGHMEM | + +----------+-----------------------+--------------------------+ + + +With a kernel built with ZONE_DMA disabled and ZONE_DMA32 enabled and booted +with `movablecore=80%` parameter on an arm64 machine with 16 Gbytes of RAM +equally split between two nodes, there will be ZONE_DMA32, ZONE_NORMAL and +ZONE_MOVABLE on node 0, and ZONE_NORMAL and ZONE_MOVABLE on node 1:: + + + 1G 9G 17G + +--------------------------------+ +--------------------------+ + | node 0 | | node 1 | + +--------------------------------+ +--------------------------+ + + 1G 4G 4200M 9G 9320M 17G + +---------+----------+-----------+ +------------+-------------+ + | DMA32 | NORMAL | MOVABLE | | NORMAL | MOVABLE | + +---------+----------+-----------+ +------------+-------------+ + +.. _nodes: + +Nodes +===== + +As we have mentioned, each node in memory is described by a ``pg_data_t`` which +is a typedef for a ``struct pglist_data``. When allocating a page, by default +Linux uses a node-local allocation policy to allocate memory from the node +closest to the running CPU. As processes tend to run on the same CPU, it is +likely the memory from the current node will be used. The allocation policy can +be controlled by users as described in +`Documentation/admin-guide/mm/numa_memory_policy.rst`. + +Most NUMA architectures maintain an array of pointers to the node +structures. The actual structures are allocated early during boot when +architecture specific code parses the physical memory map reported by the +firmware. The bulk of the node initialization happens slightly later in the +boot process by free_area_init() function, described later in Section +:ref:`Initialization `. + + +Along with the node structures, kernel maintains an array of ``nodemask_t`` +bitmasks called `node_states`. Each bitmask in this array represents a set of +nodes with particular properties as defined by `enum node_states`: + +`N_POSSIBLE` + The node could become online at some point. +`N_ONLINE` + The node is online. +`N_NORMAL_MEMORY` + The node has regular memory. +`N_HIGH_MEMORY` + The node has regular or high memory. When ``CONFIG_HIGHMEM`` is disabled + aliased to `N_NORMAL_MEMORY`. +`N_MEMORY` + The node has memory(regular, high, movable) +`N_CPU` + The node has one or more CPUs + +For each node that has a property described above, the bit corresponding to the +node ID in the ``node_states[]`` bitmask is set. + +For example, for node 2 with normal memory and CPUs, bit 2 will be set in :: + + node_states[N_POSSIBLE] + node_states[N_ONLINE] + node_states[N_NORMAL_MEMORY] + node_states[N_MEMORY] + node_states[N_CPU] + +For various operations possible with nodemasks please refer to +`include/linux/nodemask.h +`_. + +Among other things, nodemasks are used to provide macros for node traversal, +namely `for_each_node()` and `for_each_online_node()`. + +For instance, to call a function foo() for each online node:: + + for_each_online_node(nid) { + pg_data_t *pgdat = NODE_DATA(nid); + + foo(pgdat); + } + +Node structure +-------------- + +The struct pglist_data is declared in `include/linux/mmzone.h +`_. +Here we briefly describe fields of this structure: + +General +~~~~~~~ + +`node_zones` + The zones for this node. Not all of the zones may be populated, but it is + the full list. It is referenced by this node's node_zonelists as well as + other node's node_zonelists. + +`node_zonelists` The list of all zones in all nodes. This list defines the + order of zones that allocations are preferred from. The `node_zonelists` is + set up by build_zonelists() in mm/page_alloc.c during the initialization of + core memory management structures. + +`nr_zones` + Number of populated zones in this node. + +`node_mem_map` + For UMA systems that use FLATMEM memory model the 0's node (and the only) + `node_mem_map` is array of struct pages representing each physical frame. + +`node_page_ext` + For UMA systems that use FLATMEM memory model the 0's (and the only) node + `node_mem_map` is array of extensions of struct pages. Available only in the + kernels built with ``CONFIG_PAGE_EXTENTION`` enabled. + +`node_start_pfn` + The page frame number of the starting page frame in this node. + +`node_present_pages` + Total number of physical pages present in this node. + +`node_spanned_pages` + Total size of physical page range, including holes. + +`node_size_lock` + A lock that protects the fields defining the node extents. Only defined when + at least one of ``CONFIG_MEMORY_HOTPLUG`` or + ``CONFIG_DEFERRED_STRUCT_PAGE_INIT`` configuration options are enabled. + + pgdat_resize_lock() and pgdat_resize_unlock() are provided to manipulate + node_size_lock without checking for CONFIG_MEMORY_HOTPLUG or + CONFIG_DEFERRED_STRUCT_PAGE_INIT. + +`node_id` + The Node ID (NID) of the node, starts at 0. + +`totalreserve_pages` + This is a per~node reserve of pages that are not available to userspace + allocations. + +`first_deferred_pfn` + If memory initialization on large machines is deferred then this is the first + PFN that needs to be initialized. Defined only when + ``CONFIG_DEFERRED_STRUCT_PAGE_INIT`` is enabled + +`deferred_split_queue` + Per-node queue of huge pages that their split was deferred. Defined only when ``CONFIG_TRANSPARENT_HUGEPAGE`` is enabled. + +`__lruvec` + Per-node lruvec holding LRU lists and related parameters. Used only when memory cgroups are disabled. Should not be accessed directly, use mem_cgroup_lruvec() to look up lruvecs instead. + +Reclaim control +~~~~~~~~~~~~~~~ + +See also :ref:`Page Reclaim `. + +`kswapd` + Per-node instance of kswapd kernel thread. + +`kswapd_wait`, `pfmemalloc_wait`, `reclaim_wait` + Workqueues used to synchronize memory reclaim tasks + +`nr_writeback_throttled` + Number of tasks that are throttled waiting on dirty pages to clean. + +`nr_reclaim_start` + Number of pages written while reclaim is throttled waiting for writeback. + +`kswapd_order` + Controls the order kswapd tries to reclaim + +`kswapd_highest_zoneidx` + The highest zone index to be reclaimed by kswapd + +`kswapd_failures` + Number of runs kswapd was unable to reclaim any pages + +`min_unmapped_pages` + Minimal number of unmapped file backed pages that cannot be reclaimed. Determined by vm.min_unmapped_ratio sysctl. + Only defined when ``CONFIG_NUMA`` is enabled. + +`min_slab_pages` + Minimal number of SLAB pages that cannot be reclaimed. Determined by vm.min_slab_ratio sysctl. + Only defined when ``CONFIG_NUMA`` is enabled + +`flags` + Flags controlling reclaim behavior. + +Compaction control +~~~~~~~~~~~~~~~~~~ + +`kcompactd_max_order` + Page order that kcompactd should try to achieve. + +`kcompactd_highest_zoneidx` + The highest zone index to be compacted by kcompactd. + +`kcompactd_wait` + Workqueue used to synchronizes memory compaction tasks. + +`kcompactd` + Per-node instance of kcompactd kernel thread. + +`proactive_compact_trigger` + Determines if proactive compaction is enabled. Controlled by vm.compaction_proactiveness sysctl. + +Statistics +~~~~~~~~~~ + +`per_cpu_nodestats` + Per-CPU VM statistics for the node + +`vm_stat` + VM statistics for the node. + +.. _zones: + +Zones +===== + +.. _pages: + +Pages +===== + +.. _folios: + +Folios +====== + +.. _initialization: + +Initialization +==============