From nobody Sat Oct 4 00:32:09 2025 Received: from szxga05-in.huawei.com (szxga05-in.huawei.com [45.249.212.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 31FC42F6170 for ; Fri, 22 Aug 2025 09:48:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.191 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755856095; cv=none; b=PUv996+O4VpeLaHnGEBUY8GUwvDmIEH81OtXAKnNEuHvgSsB+daw0Vxb7kpJCAzqQoLD3KWemEVh3Lq34VziH5BLP14+EemQlWNtNhtWAnda8V0ZbrM4JJTdI19avZh01joTarXt0uL9quO8dF2w6F+17mf9g/GBjtnlxHtWKBM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755856095; c=relaxed/simple; bh=bOdxSrOvnNtm9n+/5utxfhd9zAJTC7p0Q1EKvGCzb+c=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=u4gfSL5cWQT2kJ3E/FxsI+Tv+RoKlOJ+3eQW8bFMUdg4EGobDUcdGKa594Mdi+8PW5282j6h+WjsP7jRLAcy5C2qxSxlIXzigITT+w6nj3lAA2dSkSGZ6bBVbsjAg8Fg97CqbRyj9d1E4Qi5QhYgPBafVBsYkvUmGGLIuCqetWU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=45.249.212.191 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.19.88.234]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4c7Zzz4d4Lz24hr6; Fri, 22 Aug 2025 17:45:19 +0800 (CST) Received: from dggpemf200018.china.huawei.com (unknown [7.185.36.31]) by mail.maildlp.com (Postfix) with ESMTPS id D12B0140109; Fri, 22 Aug 2025 17:48:10 +0800 (CST) Received: from huawei.com (10.50.85.135) by dggpemf200018.china.huawei.com (7.185.36.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 22 Aug 2025 17:48:10 +0800 From: Quanmin Yan To: CC: , , , , , , Subject: [PATCH v2 08/11] Docs/mm/damon/design: document 'address unit' parameter Date: Fri, 22 Aug 2025 17:34:16 +0800 Message-ID: <20250822093420.2103803-9-yanquanmin1@huawei.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20250822093420.2103803-1-yanquanmin1@huawei.com> References: <20250822093420.2103803-1-yanquanmin1@huawei.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: kwepems500002.china.huawei.com (7.221.188.17) To dggpemf200018.china.huawei.com (7.185.36.31) Content-Type: text/plain; charset="utf-8" From: SeongJae Park Add 'addr_unit' parameter description on DAMON design document. Signed-off-by: SeongJae Park Signed-off-by: Quanmin Yan Reviewed-by: SeongJae Park --- Documentation/mm/damon/design.rst | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/des= ign.rst index 2f6ba5c7f4c7..d9d5baa1ec87 100644 --- a/Documentation/mm/damon/design.rst +++ b/Documentation/mm/damon/design.rst @@ -67,7 +67,7 @@ processes, NUMA nodes, files, and backing memory devices = would be supportable. Also, if some architectures or devices support special optimized access ch= eck features, those will be easily configurable. =20 -DAMON currently provides below three operation sets. Below two subsections +DAMON currently provides below three operation sets. Below three subsecti= ons describe how those work. =20 - vaddr: Monitor virtual address spaces of specific processes @@ -135,6 +135,18 @@ the interference is the responsibility of sysadmins. = However, it solves the conflict with the reclaim logic using ``PG_idle`` and ``PG_young`` page fl= ags, as Idle page tracking does. =20 +Address Unit +------------ + +DAMON core layer uses ``unsinged long`` type for monitoring target address +ranges. In some cases, the address space for a given operations set could= be +too large to be handled with the type. ARM (32-bit) with large physical +address extension is an example. For such cases, a per-operations set +parameter called ``address unit`` is provided. It represents the scale fa= ctor +that need to be multiplied to the core layer's address for calculating real +address on the given address space. Support of ``address unit`` parameter= is +up to each operations set implementation. ``paddr`` is the only operation= s set +implementation that supports the parameter. =20 .. _damon_core_logic: =20 --=20 2.43.0