From: "Cristian Rodríguez" <cristian@rodriguez.im>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
Cupertino Miranda <cupertino.miranda@oracle.com>
Subject: Re: [PATCH] nptl: Disable THP on thread stack if it incurs in large RSS usage
Date: Mon, 11 Mar 2024 21:55:06 -0300 [thread overview]
Message-ID: <CAPBLoAcTvjEZ_hU1XHj3HozZbgqoD1VCa-xULussam3CM67HNQ@mail.gmail.com> (raw)
In-Reply-To: <87v879ybhv.fsf@oldenburg.str.redhat.com>
> > Do you have a link for this discussion?
>
> My message is here:
>
> <https://lore.kernel.org/all/878r46ym4b.fsf@oldenburg.str.redhat.com/>
>
> Thanks,
> Florian
Kernel 6.8 was released and the change remains in place. IMHO libc
should behave if MADV_NOHUGEPAGE was set for old kernels so the
behaviour is consistent old vs new.
next prev parent reply other threads:[~2024-03-12 0:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 17:24 Adhemerval Zanella
2023-05-03 12:42 ` Wilco Dijkstra
2023-05-15 17:57 ` Adhemerval Zanella Netto
2023-05-16 15:38 ` Wilco Dijkstra
2023-05-16 16:35 ` Adhemerval Zanella Netto
2023-05-17 12:49 ` Wilco Dijkstra
2023-05-17 13:12 ` Cupertino Miranda
2023-05-17 13:20 ` Adhemerval Zanella Netto
2023-05-17 14:22 ` Wilco Dijkstra
2023-05-17 16:50 ` Adhemerval Zanella Netto
2023-05-17 18:16 ` Wilco Dijkstra
2023-05-18 13:04 ` Adhemerval Zanella Netto
2023-05-23 9:48 ` Wilco Dijkstra
2024-01-31 2:03 ` Cristian Rodríguez
2024-01-31 7:54 ` Florian Weimer
2024-01-31 11:30 ` Adhemerval Zanella Netto
2024-01-31 11:43 ` Florian Weimer
2024-03-12 0:55 ` Cristian Rodríguez [this message]
2024-01-31 15:18 ` Cristian Rodríguez
2024-02-01 1:26 ` Cristian Rodríguez
2023-05-16 14:30 ` 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=CAPBLoAcTvjEZ_hU1XHj3HozZbgqoD1VCa-xULussam3CM67HNQ@mail.gmail.com \
--to=cristian@rodriguez.im \
--cc=Wilco.Dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=cupertino.miranda@oracle.com \
--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).