From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Jules Maselbas <jmaselbas@zdiv.net>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] common: make TLSF the default allocator
Date: Thu, 27 Mar 2025 12:37:53 +0100 [thread overview]
Message-ID: <20250327113753.361094-1-a.fatoum@pengutronix.de> (raw)
Going by the most used defconfigs (multi_*_defconfig), TLSF is the most
used allocator and it supports features absent in dlmalloc like
multiple pools (used on ARMv7-R) and has KASAN integration, so there's
even less reason to use dlmalloc nowadays.
In preparation for possible removal of dlmalloc in future, switch the
default away from dlmalloc.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
common/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/common/Kconfig b/common/Kconfig
index ddc76b2033b2..f0cd2f0729a4 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -312,6 +312,7 @@ config EXPERIMENTAL
choice
prompt "malloc implementation"
+ default MALLOC_TLSF
config MALLOC_DLMALLOC
bool "dlmalloc"
--
2.39.5
next reply other threads:[~2025-03-27 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 11:37 Ahmad Fatoum [this message]
2025-03-31 7:29 ` Sascha Hauer
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=20250327113753.361094-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jmaselbas@zdiv.net \
/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