public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] malloc: Correct the documentation of the top_pad default
Date: Thu, 4 Aug 2022 10:51:22 -0400	[thread overview]
Message-ID: <9ddb2422-47f5-ba9a-e7a3-d9522d80719a@gotplt.org> (raw)
In-Reply-To: <87wnbojswh.fsf@oldenburg.str.redhat.com>

On 2022-08-04 04:48, Florian Weimer via Libc-alpha wrote:
> DEFAULT_TOP_PAD is defined as 131072 in
> sysdeps/generic/malloc-machine.h.

LGTM, but I wonder if we should tighten this so that it doesn't appear 
that DEFAULT_TOP_PAD could be 0 in any of our build configurations. 
e.g. we could replace the definition with a #error "define 
DEFAULT_TOP_PAD" or something like that to ensure that it's always 
defined through malloc-machine.h.  What do you think?

Thanks,
Sid

> 
> ---
>   elf/dl-tunables.list           | 1 +
>   elf/tst-rtld-list-tunables.exp | 2 +-
>   manual/tunables.texi           | 2 +-
>   3 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/elf/dl-tunables.list b/elf/dl-tunables.list
> index e6a56b3070..e925590c36 100644
> --- a/elf/dl-tunables.list
> +++ b/elf/dl-tunables.list
> @@ -42,6 +42,7 @@ glibc {
>         type: SIZE_T
>         env_alias: MALLOC_TOP_PAD_
>         security_level: SXID_IGNORE
> +      default: 131072
>       }
>       perturb {
>         type: INT_32
> diff --git a/elf/tst-rtld-list-tunables.exp b/elf/tst-rtld-list-tunables.exp
> index cdfdb56a94..2233ea9c7c 100644
> --- a/elf/tst-rtld-list-tunables.exp
> +++ b/elf/tst-rtld-list-tunables.exp
> @@ -9,7 +9,7 @@ glibc.malloc.perturb: 0 (min: 0, max: 255)
>   glibc.malloc.tcache_count: 0x0 (min: 0x0, max: 0x[f]+)
>   glibc.malloc.tcache_max: 0x0 (min: 0x0, max: 0x[f]+)
>   glibc.malloc.tcache_unsorted_limit: 0x0 (min: 0x0, max: 0x[f]+)
> -glibc.malloc.top_pad: 0x0 (min: 0x0, max: 0x[f]+)
> +glibc.malloc.top_pad: 0x20000 (min: 0x0, max: 0x[f]+)
>   glibc.malloc.trim_threshold: 0x0 (min: 0x0, max: 0x[f]+)
>   glibc.rtld.dynamic_sort: 2 (min: 1, max: 2)
>   glibc.rtld.nns: 0x4 (min: 0x1, max: 0x10)
> diff --git a/manual/tunables.texi b/manual/tunables.texi
> index 83cdcdac6d..ffd50a3fe2 100644
> --- a/manual/tunables.texi
> +++ b/manual/tunables.texi
> @@ -143,7 +143,7 @@ number of bytes to retain when shrinking any of the arenas.  This provides the
>   necessary hysteresis in heap size such that excessive amounts of system calls
>   can be avoided.
>   
> -The default value of this tunable is @samp{0}.
> +The default value of this tunable is @samp{131072} (128 KB).
>   @end deftp
>   
>   @deftp Tunable glibc.malloc.perturb
> 

  reply	other threads:[~2022-08-04 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  8:48 Florian Weimer
2022-08-04 14:51 ` Siddhesh Poyarekar [this message]
2022-08-04 15:14   ` Florian Weimer
2022-08-04 15:15     ` Siddhesh Poyarekar
2022-08-04 15:46 ` Alejandro Colomar
2022-08-04 15:54   ` Florian Weimer

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=9ddb2422-47f5-ba9a-e7a3-d9522d80719a@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=fweimer@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).