public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Cupertino Miranda <cupertino.miranda@oracle.com>
To: libc-alpha@sourceware.org
Cc: jose.marchesi@oracle.com, elena.zannoni@oracle.com,
	adhemerval.zanella@linaro.org
Subject: [PATCH] Created tunable to force small pages on stack allocation.
Date: Fri, 10 Mar 2023 14:35:57 +0000	[thread overview]
Message-ID: <20230310143558.361825-1-cupertino.miranda@oracle.com> (raw)

Hi everyone,

This patch is the result of the following RFC:
https://sourceware.org/pipermail/libc-alpha/2023-March/146203.html

It introduces the tunable glibc.pthread.stack_hugetlb to control when
stack allocation should be allowed to be mapped in hugetls.
The purpose of this tunable is to allow better control on RSS for
applications/systems that rely on having hugepages enabled, for
performance reasons, but still wish to want to keep RSS to a minimal
when allocating lots of threads.

Looking forward to your comments and suggestions.

Best regards,
Cupertino



             reply	other threads:[~2023-03-10 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 14:35 Cupertino Miranda [this message]
2023-03-10 14:35 ` Cupertino Miranda
2023-03-13  7:54   ` Florian Weimer
2023-03-13 10:07     ` Cupertino Miranda
2023-03-13 17:10       ` Cupertino Miranda
2023-03-13 17:18         ` Cupertino Miranda
2023-03-13 17:15       ` Adhemerval Zanella Netto
2023-03-13 17:32         ` Cupertino Miranda
2023-03-13 17:17     ` Cupertino Miranda
2023-03-20 15:41 [v2] Created tunable to force small pages on stack Cupertino Miranda
2023-03-20 15:41 ` [PATCH] Created tunable to force small pages on stack allocation Cupertino Miranda

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=20230310143558.361825-1-cupertino.miranda@oracle.com \
    --to=cupertino.miranda@oracle.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=elena.zannoni@oracle.com \
    --cc=jose.marchesi@oracle.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).