From: SeongJae Park <sj@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: SeongJae Park <sj@kernel.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH RFC 2/2] mm/cma: Consolidate accounting in dedicated functions
Date: Mon, 17 Nov 2025 17:40:20 -0800 [thread overview]
Message-ID: <20251118014021.75804-1-sj@kernel.org> (raw)
In-Reply-To: <20251117121502.6db0fd7a@endymion>
On Mon, 17 Nov 2025 12:15:02 +0100 Jean Delvare <jdelvare@suse.de> wrote:
> Move all accounting to dedicated functions and rename them
> accordingly.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
Reviewed-by: SeongJae Park <sj@kernel.org>
> ---
> This is based on a suggestion by SeongJae Park. Comments welcome.
>
> mm/cma.c | 43 ++++++++++++++++++-------------------------
> 1 file changed, 18 insertions(+), 25 deletions(-)
>
> --- linux-6.17.orig/mm/cma.c
> +++ linux-6.17/mm/cma.c
[...]
> @@ -1029,7 +1022,7 @@ bool cma_release(struct cma *cma, const
>
> free_contig_range(pfn, count);
> cma_clear_bitmap(cma, cmr, pfn, count);
> - cma_sysfs_account_release_pages(cma, count);
> + cma_account_release(cma, count);
> trace_cma_release(cma->name, pfn, pages, count);
I was thinking we could further move trace_*() function calls to the new
functions, but this version also looks good to me.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-11-18 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 10:56 [PATCH v2 1/2] mm/cma: Inline cma_sysfs counter hooks Jean Delvare
2025-11-17 11:15 ` [PATCH RFC 2/2] mm/cma: Consolidate accounting in dedicated functions Jean Delvare
2025-11-18 1:40 ` SeongJae Park [this message]
2025-11-17 11:22 ` [PATCH v2 1/2] mm/cma: Inline cma_sysfs counter hooks David Hildenbrand (Red Hat)
2025-11-18 1:34 ` SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251118014021.75804-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=david@redhat.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.