From patchwork Tue Feb 22 17:01:00 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: SeongJae Park X-Patchwork-Id: 12755688 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 7F547C433EF for ; Tue, 22 Feb 2022 17:01:17 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id F23A58D0006; Tue, 22 Feb 2022 12:01:15 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id EAB8F8D0001; Tue, 22 Feb 2022 12:01:15 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D23B88D0006; Tue, 22 Feb 2022 12:01:15 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.25]) by kanga.kvack.org (Postfix) with ESMTP id BE06F8D0001 for ; Tue, 22 Feb 2022 12:01:15 -0500 (EST) Received: from smtpin09.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay12.hostedemail.com (Postfix) with ESMTP id 8B811120F3A for ; Tue, 22 Feb 2022 17:01:15 +0000 (UTC) X-FDA: 79171031310.09.2ECA33D Received: from sin.source.kernel.org (sin.source.kernel.org [145.40.73.55]) by imf10.hostedemail.com (Postfix) with ESMTP id 6EF5FC0012 for ; Tue, 22 Feb 2022 17:01:13 +0000 (UTC) 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 sin.source.kernel.org (Postfix) with ESMTPS id 633CECE17AA; Tue, 22 Feb 2022 17:01:10 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 60D93C340F9; Tue, 22 Feb 2022 17:01:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1645549268; bh=U1WoaJ7lbnns8naY/1+W0bLu1qPxUeglQsjIh920zbo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=q0f6a+m7QBkb6m90qVbP/bQOXJLehC8assGKbnwnzG2ooCM4dGXeX8GNBtnNjIHNa GxFtRJMWSSZzeVZay9Ntg+FgiMvHS83XYziKa80YKhc4JesxqjmML309ul0D7oVpIT 7Uc9L+NvEhAtjo99Hc9O7/nnqq4Ak32j066QgxSqODSbd85lpwptVuC/OFNgdi12bM lEE6cJmAmYtyPsDnzifcqjev5KHMf9bso+KfAK3ZwX3bDOp1zLFv0F9GQDkXiXd89j 9zaqyHlqyG1wj1qsOYKCyWYNgux8NGalLPzUraP9Vy3P4WsNTX/6iBdFH/KmSiFNtY PA0+s26xkEsxA== From: SeongJae Park To: akpm@linux-foundation.org Cc: corbet@lwn.net, linux-mm@kvack.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, SeongJae Park Subject: [PATCH 3/3] Docs/damon: Update outdated term 'regions update interval' Date: Tue, 22 Feb 2022 17:01:00 +0000 Message-Id: <20220222170100.17068-4-sj@kernel.org> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220222170100.17068-1-sj@kernel.org> References: <20220222170100.17068-1-sj@kernel.org> X-Rspam-User: Authentication-Results: imf10.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=q0f6a+m7; spf=pass (imf10.hostedemail.com: domain of sj@kernel.org designates 145.40.73.55 as permitted sender) smtp.mailfrom=sj@kernel.org; dmarc=pass (policy=none) header.from=kernel.org X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: 6EF5FC0012 X-Stat-Signature: cohoqxcfkcko6gfb1qouhaupf8gijynb X-HE-Tag: 1645549273-259501 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000028, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Before DAMON is merged in the mainline, the concept of 'regions update interval' has generalized to be used as the time interval for update of any monitoring operations related data structure, but the document has not updated properly. This commit updates the document for better consistency. Signed-off-by: SeongJae Park --- Documentation/admin-guide/mm/damon/usage.rst | 6 +++--- Documentation/vm/damon/design.rst | 12 +++++++----- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/Documentation/admin-guide/mm/damon/usage.rst b/Documentation/admin-guide/mm/damon/usage.rst index 1e06435b8ff6..b6ec650873b2 100644 --- a/Documentation/admin-guide/mm/damon/usage.rst +++ b/Documentation/admin-guide/mm/damon/usage.rst @@ -47,7 +47,7 @@ Attributes ---------- Users can get and set the ``sampling interval``, ``aggregation interval``, -``regions update interval``, and min/max number of monitoring target regions by +``update interval``, and min/max number of monitoring target regions by reading from and writing to the ``attrs`` file. To know about the monitoring attributes in detail, please refer to the :doc:`/vm/damon/design`. For example, below commands set those values to 5 ms, 100 ms, 1,000 ms, 10 and @@ -128,8 +128,8 @@ ranges, ``20-40`` and ``50-100`` as that of pid 4242, which is the second one Note that this sets the initial monitoring target regions only. In case of virtual memory monitoring, DAMON will automatically updates the boundary of the -regions after one ``regions update interval``. Therefore, users should set the -``regions update interval`` large enough in this case, if they don't want the +regions after one ``update interval``. Therefore, users should set the +``update interval`` large enough in this case, if they don't want the update. diff --git a/Documentation/vm/damon/design.rst b/Documentation/vm/damon/design.rst index bba89632e924..0cff6fac6b7e 100644 --- a/Documentation/vm/damon/design.rst +++ b/Documentation/vm/damon/design.rst @@ -95,8 +95,8 @@ Address Space Independent Core Mechanisms Below four sections describe each of the DAMON core mechanisms and the five monitoring attributes, ``sampling interval``, ``aggregation interval``, -``regions update interval``, ``minimum number of regions``, and ``maximum -number of regions``. +``update interval``, ``minimum number of regions``, and ``maximum number of +regions``. Access Frequency Monitoring @@ -169,6 +169,8 @@ The monitoring target address range could dynamically changed. For example, virtual memory could be dynamically mapped and unmapped. Physical memory could be hot-plugged. -As the changes could be quite frequent in some cases, DAMON checks the dynamic -memory mapping changes and applies it to the abstracted target area only for -each of a user-specified time interval (``regions update interval``). +As the changes could be quite frequent in some cases, DAMON allows the +monitoring operations to check dynamic changes including memory mapping changes +and applies it to monitoring operations-related data structures such as the +abstracted monitoring target memory area only for each of a user-specified time +interval (``update interval``).