Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp513449rwd; Wed, 24 May 2023 23:14:22 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5/+GAMOiX2V4iu1U8hm8CsYm74ahR+x0js0nADw+AHuD+KyL3XYlCkxbcsxvVtVjVYVQm2 X-Received: by 2002:a05:6a00:1344:b0:643:85a0:57fe with SMTP id k4-20020a056a00134400b0064385a057femr8160238pfu.2.1684995262332; Wed, 24 May 2023 23:14:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684995262; cv=none; d=google.com; s=arc-20160816; b=0rmdm1vIH6TLUZQdnC0m60Qeuk+lkVEb83H+ujAfjE57F0liSBDz99KrGobgEukeQZ FyLwrZ9twWGW2RPCwoteF514gEXCCpq59+iG8qO4x3P6kOle+ih/0bh745sZe8PHQWSN sD2EbssZO8LWqS81ttZZZs1oLf0e7TMFzMn5+AIkw0mTi5mPNMLmA6EhojSZdKrPhGSI /+KV0hC+VyJaC4oBt9+x/EWcdgVZrl2B421Vh0qMYo2EQYbnYLfmQTn+jPPn1vA27Bp+ V4ZzeD64iJM3jk/1B7xlLvGvMswR6Zmrc2KMujVVZMrZM18HKN5UL1+KWGZSqNnLKEOO PKKQ== 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; bh=/IGz+EOJ6ZJOoVXa4iGXtocLRze/sO07dBQARymqz/w=; b=oXK/nneHJpYYUzbVdNmThWDhqTqUAP/U79ZcSKG/c9U5+/bgB8Qw+UtdkFvyHv1uHu gV6CUENtSB7HeNagE0v63HAlhD9cijv+zqIRQE/7KUphhsgpbEK96lUme+AGrzKf/JJf gtuSYEXYRON86Nq30lZpvzXIxD2Wime0M15K7/guX6px8e/Rr4nu6p+VJkNL/loYebuX LIRyXB7ZpjZwJbe3Ya7TiOigVMEu/hVWpF4L9bx24qXs0UOR6RhR+39NUzLt6oIzJhht 6z81KqknanLFmrQDvp5zs+lg5VFdHxNDQWkUy6zKTgczlL1PC6v3Fo0Ky3TiBMC3ciYt pxjQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=zte.com.cn Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d7-20020aa797a7000000b0063b52b9a8f5si704309pfq.267.2023.05.24.23.14.09; Wed, 24 May 2023 23:14:22 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=zte.com.cn Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237549AbjEYFyh (ORCPT + 99 others); Thu, 25 May 2023 01:54:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52980 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237630AbjEYFy0 (ORCPT ); Thu, 25 May 2023 01:54:26 -0400 Received: from ubuntu20 (unknown [193.203.214.57]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9D39E132 for ; Wed, 24 May 2023 22:54:04 -0700 (PDT) Received: by ubuntu20 (Postfix, from userid 1003) id 2AA0DE1D15; Thu, 25 May 2023 13:54:03 +0800 (CST) From: Yang Yang To: akpm@linux-foundation.org, david@redhat.com Cc: yang.yang29@zte.com.cn, imbrenda@linux.ibm.com, jiang.xuexin@zte.com.cn, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ran.xiaokai@zte.com.cn, xu.xin.sc@gmail.com, xu.xin16@zte.com.cn, shr@devkernel.io Subject: [PATCH v10 4/5] ksm: consider KSM-placed zeropages when calculating KSM profit Date: Thu, 25 May 2023 13:54:01 +0800 Message-Id: <20230525055401.27375-1-yang.yang29@zte.com.cn> X-Mailer: git-send-email 2.25.1 In-Reply-To: <202305251341580149313@zte.com.cn> References: <202305251341580149313@zte.com.cn> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=3.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,FSL_HELO_NON_FQDN_1, HEADER_FROM_DIFFERENT_DOMAINS,HELO_NO_DOMAIN,NO_DNS_FOR_FROM, RCVD_IN_PBL,RDNS_NONE,SPF_SOFTFAIL,SPOOFED_FREEMAIL_NO_RDNS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: *** 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 From: xu xin When use_zero_pages is enabled, the calculation of ksm profit is not correct because ksm zero pages is not counted in. So update the calculation of KSM profit including the documentation. Signed-off-by: xu xin Acked-by: David Hildenbrand Cc: Xiaokai Ran Cc: Yang Yang Cc: Jiang Xuexin Cc: Claudio Imbrenda --- Documentation/admin-guide/mm/ksm.rst | 18 +++++++++++------- mm/ksm.c | 4 ++-- 2 files changed, 13 insertions(+), 9 deletions(-) diff --git a/Documentation/admin-guide/mm/ksm.rst b/Documentation/admin-guide/mm/ksm.rst index 6cc919dbfd55..5c5be7bd84b8 100644 --- a/Documentation/admin-guide/mm/ksm.rst +++ b/Documentation/admin-guide/mm/ksm.rst @@ -203,21 +203,25 @@ several times, which are unprofitable memory consumed. 1) How to determine whether KSM save memory or consume memory in system-wide range? Here is a simple approximate calculation for reference:: - general_profit =~ pages_sharing * sizeof(page) - (all_rmap_items) * + general_profit =~ ksm_saved_pages * sizeof(page) - (all_rmap_items) * sizeof(rmap_item); - where all_rmap_items can be easily obtained by summing ``pages_sharing``, - ``pages_shared``, ``pages_unshared`` and ``pages_volatile``. + where ksm_saved_pages equals to the sum of ``pages_sharing`` + + ``ksm_zero_pages`` of the system, and all_rmap_items can be easily + obtained by summing ``pages_sharing``, ``pages_shared``, ``pages_unshared`` + and ``pages_volatile``. 2) The KSM profit inner a single process can be similarly obtained by the following approximate calculation:: - process_profit =~ ksm_merging_pages * sizeof(page) - + process_profit =~ ksm_saved_pages * sizeof(page) - ksm_rmap_items * sizeof(rmap_item). - where ksm_merging_pages is shown under the directory ``/proc//``, - and ksm_rmap_items is shown in ``/proc//ksm_stat``. The process profit - is also shown in ``/proc//ksm_stat`` as ksm_process_profit. + where ksm_saved_pages equals to the sum of ``ksm_merging_pages`` and + ``ksm_zero_pages``, both of which are shown under the directory + ``/proc//ksm_stat``, and ksm_rmap_items is also shown in + ``/proc//ksm_stat``. The process profit is also shown in + ``/proc//ksm_stat`` as ksm_process_profit. From the perspective of application, a high ratio of ``ksm_rmap_items`` to ``ksm_merging_pages`` means a bad madvise-applied policy, so developers or diff --git a/mm/ksm.c b/mm/ksm.c index 07a6fe7d7c99..1c7d0e215c47 100644 --- a/mm/ksm.c +++ b/mm/ksm.c @@ -3090,7 +3090,7 @@ static void wait_while_offlining(void) #ifdef CONFIG_PROC_FS long ksm_process_profit(struct mm_struct *mm) { - return mm->ksm_merging_pages * PAGE_SIZE - + return (long)(mm->ksm_merging_pages + mm->ksm_zero_pages) * PAGE_SIZE - mm->ksm_rmap_items * sizeof(struct ksm_rmap_item); } #endif /* CONFIG_PROC_FS */ @@ -3371,7 +3371,7 @@ static ssize_t general_profit_show(struct kobject *kobj, { long general_profit; - general_profit = ksm_pages_sharing * PAGE_SIZE - + general_profit = (ksm_pages_sharing + ksm_zero_pages) * PAGE_SIZE - ksm_rmap_items * sizeof(struct ksm_rmap_item); return sysfs_emit(buf, "%ld\n", general_profit); -- 2.15.2