From: Cupertino Miranda <cupertino.miranda@oracle.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
libc-alpha@sourceware.org, jose.marchesi@oracle.com,
elena.zannoni@oracle.com
Subject: Re: [PATCH v6 1/1] Created tunable to force small pages on stack allocation.
Date: Thu, 20 Apr 2023 21:52:15 +0100 [thread overview]
Message-ID: <87pm7y9szk.fsf@oracle.com> (raw)
In-Reply-To: <767ab124-8448-0883-ff44-6019cec95902@linaro.org>
> I also sent an updated patch to detect when the split will always
> happen [1]. As I wrote in the patch, the tunable might still be
> required in some specific scenarios, but it would be good to have
> some heuristic to detect such scenarios if/when distros start to
> active THP to be always enabled.
>
> [1] https://patchwork.sourceware.org/project/glibc/patch/20230420172436.2013698-1-adhemerval.zanella@linaro.org/
>
I have seen it and agree that it is useful.
I will attempt to test it tomorrow if you would be interested in the
feedback. I presume the condition is very similar to what I tested
before.
next prev parent reply other threads:[~2023-04-20 20:52 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
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 [this message]
-- 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=87pm7y9szk.fsf@oracle.com \
--to=cupertino.miranda@oracle.com \
--cc=Wilco.Dijkstra@arm.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).