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: [RFC PATCH] mm/cma: Inline cma_sysfs counter hooks
Date: Fri, 14 Nov 2025 17:48:09 -0800 [thread overview]
Message-ID: <20251115014810.79376-1-sj@kernel.org> (raw)
In-Reply-To: <20251114110301.39316246@endymion>
On Fri, 14 Nov 2025 11:03:01 +0100 Jean Delvare <jdelvare@suse.de> wrote:
> Move cma_sysfs counter hooks from cma_sysfs.c to inline functions in
> cma.h. These one-liner functions are only used once each, but the
> compiler currently can't inline them because they are defined in one
> object and used in another. Letting the compiler inline these
> functions lowers the footprint and runtime cost of the sysfs interface
> to CMA stats even more.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
Acked-by: SeongJae Park <sj@kernel.org>
> ---
> Applies on top of my previous patch due to a context change, but
> otherwise independent thereof.
>
> On second thought, we might as well move these functions to cma.c as
> this is the only place where they are called, so it's hard to justify
> why they should be in a header file. Opinions?
I think that should also be nice. In the case, I think it can drop 'inline'
keyword to let the compiler makes good decisions with its nice knowledge. Also
the similar event accounting code such as count_vm_event() and trace_*() calls
can be moved into the new function together. If do so, the function name may
also better to be updated to represent it is not only for cma sysfs but general
events accounting. Just my two cents.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-11-15 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 10:03 [RFC PATCH] mm/cma: Inline cma_sysfs counter hooks Jean Delvare
2025-11-15 1:48 ` SeongJae Park [this message]
2025-11-17 10:49 ` Jean Delvare
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=20251115014810.79376-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).