From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Remove --disable-experimental-malloc option
Date: Wed, 29 Mar 2023 08:54:00 -0300 [thread overview]
Message-ID: <74067409-32ed-eead-e73a-47c6c88a9473@linaro.org> (raw)
In-Reply-To: <xntty4y88i.fsf@greed.delorie.com>
On 28/03/23 16:41, DJ Delorie wrote:
> Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
>> -'--disable-experimental-malloc'
>> - By default, a per-thread cache is enabled in 'malloc'. While this
>> - cache can be disabled on a per-application basis using tunables
>> - (set glibc.malloc.tcache_count to zero), this option can be used to
>> - remove it from the build completely.
>> -
>
> Ok. Also, yay :-)
>
>> CPPFLAGS-malloc-debug.c += -DUSE_TCACHE=0
>> -ifeq ($(experimental-malloc),yes)
>> CPPFLAGS-malloc.c += -DUSE_TCACHE=1
>> -else
>> -CPPFLAGS-malloc.c += -DUSE_TCACHE=0
>> -endif
>
> In the future, we could default this inside malloc.c instead of doing
> this in the Makefile, but it's not important now. Ok.
>
>> diff --git a/manual/install.texi b/manual/install.texi
>> index 260f8a5c82..cb76fbd28f 100644
>> --- a/manual/install.texi
>> +++ b/manual/install.texi
>> @@ -292,12 +292,6 @@ This option is for hackers and distributions experimenting with
>> independently-maintained implementations of libcrypt. It may become
>> the default in a future release.
>>
>> -@item --disable-experimental-malloc
>> -By default, a per-thread cache is enabled in @code{malloc}. While
>> -this cache can be disabled on a per-application basis using tunables
>> -(set glibc.malloc.tcache_count to zero), this option can be used to
>> -remove it from the build completely.
>> -
>
> LGTM.
> Reviewed-by: DJ Delorie <dj@redhat.com>
>
Thanks, I will add a NEW entry on deprecated and removed features:
* The --disable-experimental-malloc is no longer available. The per-thread
cache can still be disable per-application using tunables
(glibc.malloc.tcache_count set to zero).
prev parent reply other threads:[~2023-03-29 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 18:50 Adhemerval Zanella
2023-03-28 19:41 ` DJ Delorie
2023-03-29 11:54 ` Adhemerval Zanella Netto [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=74067409-32ed-eead-e73a-47c6c88a9473@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).