public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Cupertino Miranda via Libc-alpha <libc-alpha@sourceware.org>
Cc: Cupertino Miranda <cupertino.miranda@oracle.com>,
	jose.marchesi@oracle.com,  elena.zannoni@oracle.com,
	tstuefe@redhat.com
Subject: Re: [PATCH v6 1/1] Created tunable to force small pages on stack allocation.
Date: Mon, 17 Apr 2023 12:17:50 +0200	[thread overview]
Message-ID: <874jpeizht.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230414151220.52040-2-cupertino.miranda@oracle.com> (Cupertino Miranda via Libc-alpha's message of "Fri, 14 Apr 2023 16:12:20 +0100")

* Cupertino Miranda via Libc-alpha:

> Created tunable glibc.pthread.stack_hugetlb to control when hugepages
> can be used for stack allocation.
> In case THP are enabled and glibc.pthread.stack_hugetlb is set to
> 0, glibc will madvise the kernel not to use allow hugepages for stack
> allocations.

Is this for the benefit of OpenJDK (among other things)?

In this case, we should expose this in a pthread_attr_t interface as
well, so that OpenJDK can activate this easily for the required threads.
This can be done in a follow-up patch.

Thanks,
Florian


  reply	other threads:[~2023-04-17 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 15:12 [PATCH v6 0/1] *** " Cupertino Miranda
2023-04-14 15:12 ` [PATCH v6 1/1] " Cupertino Miranda
2023-04-17 10:17   ` Florian Weimer [this message]
2023-04-17 13:32     ` Cupertino Miranda
2023-04-20 16:55   ` Adhemerval Zanella Netto
2023-04-20 20:21     ` Cupertino Miranda
2023-04-20 20:33       ` Adhemerval Zanella Netto
2023-04-20 20:52         ` Cupertino Miranda
  -- strict thread matches above, loose matches on Subject: below --
2023-04-14 14:28 [PATCH v6 0/1] *** " Cupertino Miranda
2023-04-14 14:28 ` [PATCH v6 1/1] " 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=874jpeizht.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=cupertino.miranda@oracle.com \
    --cc=elena.zannoni@oracle.com \
    --cc=jose.marchesi@oracle.com \
    --cc=libc-alpha@sourceware.org \
    --cc=tstuefe@redhat.com \
    /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).