From: David Hildenbrand <david@redhat.com>
To: Jean Delvare <jdelvare@suse.de>, Minchan Kim <minchan@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Frank van der Linden <fvdl@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Minchan Kim <minchan@kernel.org>
Subject: Re: Default value of CMA_SYSFS
Date: Wed, 6 Aug 2025 10:51:37 +0200 [thread overview]
Message-ID: <9ec621c0-ab26-442e-a07d-06905699fbc6@redhat.com> (raw)
In-Reply-To: <20250806100748.21620372@endymion>
On 06.08.25 10:07, Jean Delvare wrote:
> Hi all,
Hi!
>
> CMA_SYSFS looks like a generally useful and low footprint option. Is
> there any reason why it isn't enabled by default when its dependencies
> are met?
Looking at the introducing commit
commit 43ca106fa8ec7d684776fbe561214d3b2b7cb9cb
Author: Minchan Kim <minchan@kernel.org>
Date: Tue May 4 18:37:28 2021 -0700
mm: cma: support sysfs
Since CMA is getting used more widely, it's more important to keep
monitoring CMA statistics for system health since it's directly related to
user experience.
This patch introduces sysfs statistics for CMA, in order to provide some
basic monitoring of the CMA allocator.
* the number of CMA page successful allocations
* the number of CMA page allocation failures
These two values allow the user to calcuate the allocation
failure rate for each CMA area.
I cannot really tell why we made this configurable.
>
> I was wondering if it would make sense to add "default y" to this
> option. What do you think?
I'm wondering if we should remove the option completely -- or turn it into an
internal option only such that it's no longer user-selectable.
CCing Minchan Kim
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-08-06 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 8:07 Jean Delvare
2025-08-06 8:51 ` David Hildenbrand [this message]
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=9ec621c0-ab26-442e-a07d-06905699fbc6@redhat.com \
--to=david@redhat.com \
--cc=anshuman.khandual@arm.com \
--cc=fvdl@google.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
/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