From nobody Sat Oct 4 22:39:30 2025 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) (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 585851DF725 for ; Wed, 13 Aug 2025 03:52:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.187 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755057159; cv=none; b=INrbXcQCe08o6UJ4ZWznOzEGSKDSXd75aBa4/bi0aWrVGq7jwytEZGN1reJ9M+z5w6oW7TBvgNhZ38vu7HIZL9+IBNk618qESY3fKnEoTcZ2rX7wK6Dat4Ftbdf5O+hnvZG+vakcbkK6gMsriF5cTIbSTqs3/Oznhz2gPoCbKBk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755057159; c=relaxed/simple; bh=HvU3E/EZrYOQm87rtAfpaxHK5Sj8XoCon38Ydsvh/0o=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=pTnMZ1xdNC038bWA4P3fffyHECeixn07uJwpQ01QaOF9WZHF/rnABskBaWYLcyJh1bifDH6by1MiFdTECE0LLMH+SqzX0GrWwIWyy4EWtvq/nLvlZMijJJaV1Ey/KN3L94KkCnkyvxoD4lsFtOgwqYB0eskr5WOro9QTlT3iZaY= 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.187 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.162.254]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4c1vTN04kPz14MTY; Wed, 13 Aug 2025 11:47:36 +0800 (CST) Received: from dggpemf200018.china.huawei.com (unknown [7.185.36.31]) by mail.maildlp.com (Postfix) with ESMTPS id 4F63818048D; Wed, 13 Aug 2025 11:52:35 +0800 (CST) Received: from huawei.com (10.175.113.32) 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; Wed, 13 Aug 2025 11:52:34 +0800 From: Quanmin Yan To: CC: , , , , , , Subject: [RFC PATCH -next 08/16] Docs/mm/damon/design: document 'address unit' parameter Date: Wed, 13 Aug 2025 13:06:58 +0800 Message-ID: <20250813050706.1564229-9-yanquanmin1@huawei.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20250813050706.1564229-1-yanquanmin1@huawei.com> References: <20250813050706.1564229-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: kwepems100002.china.huawei.com (7.221.188.206) 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 --- 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 03f8137256f5..cffa320ead88 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.34.1