From mboxrd@z Thu Jan 1 00:00:00 1970 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4C9CFC47422 for ; Mon, 29 Jan 2024 09:24:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=KIxzoF1ZK/09r/kyWIvFYYuG004Sw3tQDXCOdFvKztQ=; b=CRlcmfjv4swb3O F8tbz4uJn9QsmoDzHl8s1Ge4gStpjoGlVnJaVKtRdg4lqsgaFuPRcNzV1Vs/QQALGm3Ew5voHPc5n QwDELAz2r+Xjo2Ar2EveZtt4P6Pt2AZH0+xTdHRiOO4Ri+wLXN7eW9A88xN1t5ZZ04QTLvHPksloA xDwJozVEV6okME8hYNkCmwB3GWDGTQVK6vyrFZb8fVhuX6j24xNBClaniem36SXmGwRbI3T9RvQOP wMyTyz7o4FIQqeq1aNiU41CFZ6OXixa3ziE06a7uURaXfVEJS+E2Qm0hXFgu5/48UJ6vcCHT278F7 ps0EED6yEi1ap6ttYi2w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rUNse-0000000BzNn-2aCJ; Mon, 29 Jan 2024 09:24:40 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rUNsc-0000000BzN7-0MDK for linux-arm-kernel@lists.infradead.org; Mon, 29 Jan 2024 09:24:39 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 132871FB; Mon, 29 Jan 2024 01:25:18 -0800 (PST) Received: from [10.162.42.11] (a077893.blr.arm.com [10.162.42.11]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5B6393F762; Mon, 29 Jan 2024 01:24:23 -0800 (PST) Message-ID: <0a71c87a-ae2c-4a61-8adb-3a51d6369b99@arm.com> Date: Mon, 29 Jan 2024 14:54:20 +0530 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH RFC v3 06/35] mm: cma: Make CMA_ALLOC_SUCCESS/FAIL count the number of pages Content-Language: en-US To: Alexandru Elisei , catalin.marinas@arm.com, will@kernel.org, oliver.upton@linux.dev, maz@kernel.org, james.morse@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com, arnd@arndb.de, akpm@linux-foundation.org, mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de, bristot@redhat.com, vschneid@redhat.com, mhiramat@kernel.org, rppt@kernel.org, hughd@google.com Cc: pcc@google.com, steven.price@arm.com, vincenzo.frascino@arm.com, david@redhat.com, eugenis@google.com, kcc@google.com, hyesoo.yu@samsung.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev, linux-fsdevel@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org References: <20240125164256.4147-1-alexandru.elisei@arm.com> <20240125164256.4147-7-alexandru.elisei@arm.com> From: Anshuman Khandual In-Reply-To: <20240125164256.4147-7-alexandru.elisei@arm.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240129_012438_244889_C251DB2F X-CRM114-Status: GOOD ( 19.89 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 1/25/24 22:12, Alexandru Elisei wrote: > The CMA_ALLOC_SUCCESS, respectively CMA_ALLOC_FAIL, are increased by one > after each cma_alloc() function call. This is done even though cma_alloc() > can allocate an arbitrary number of CMA pages. When looking at > /proc/vmstat, the number of successful (or failed) cma_alloc() calls > doesn't tell much with regards to how many CMA pages were allocated via > cma_alloc() versus via the page allocator (regular allocation request or > PCP lists refill). > > This can also be rather confusing to a user who isn't familiar with the > code, since the unit of measurement for nr_free_cma is the number of pages, > but cma_alloc_success and cma_alloc_fail count the number of cma_alloc() > function calls. > > Let's make this consistent, and arguably more useful, by having > CMA_ALLOC_SUCCESS count the number of successfully allocated CMA pages, and > CMA_ALLOC_FAIL count the number of pages the cma_alloc() failed to > allocate. > > For users that wish to track the number of cma_alloc() calls, there are > tracepoints for that already implemented. > > Signed-off-by: Alexandru Elisei > --- > mm/cma.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/mm/cma.c b/mm/cma.c > index f49c95f8ee37..dbf7fe8cb1bd 100644 > --- a/mm/cma.c > +++ b/mm/cma.c > @@ -517,10 +517,10 @@ struct page *cma_alloc(struct cma *cma, unsigned long count, > pr_debug("%s(): returned %p\n", __func__, page); > out: > if (page) { > - count_vm_event(CMA_ALLOC_SUCCESS); > + count_vm_events(CMA_ALLOC_SUCCESS, count); > cma_sysfs_account_success_pages(cma, count); > } else { > - count_vm_event(CMA_ALLOC_FAIL); > + count_vm_events(CMA_ALLOC_FAIL, count); > if (cma) > cma_sysfs_account_fail_pages(cma, count); > } Without getting into the merits of this patch - which is actually trying to do semantics change to /proc/vmstat, wondering how is this even related to this particular series ? If required this could be debated on it's on separately. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel