From: Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org,
Norbert Manthey <nmanthey@conp-solutions.com>,
Guillaume Morin <guillaume@morinfr.org>
Subject: Re: [PATCH 0/3] malloc: improve THP effectiveness
Date: Tue, 17 Aug 2021 09:30:15 +0530 [thread overview]
Message-ID: <631f477d-c504-94d5-3141-a58263fde5c5@sourceware.org> (raw)
In-Reply-To: <8a9c54a5-d0ad-440c-75e5-3390e9cc8a44@linaro.org>
On 8/17/21 2:25 AM, Adhemerval Zanella via Libc-alpha wrote:
> I am reworking this patchset and I intend to add an option to use
> MAP_HUGETLB as well.
A low hanging fruit for adding MAP_HUGETLB may be at the mmap threshold;
whenever it crosses the hugepage size, always use MAP_HUGETLB for
mmapped blocks if the user requests it via tunable.
Siddhesh
prev parent reply other threads:[~2021-08-17 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 21:04 [PATCH 0/3] malloc: improve THP effectiveness Adhemerval Zanella via Libc-alpha
2021-08-13 21:04 ` [PATCH 1/3] malloc: Add madvise support for Transparent Huge Pages Adhemerval Zanella via Libc-alpha
2021-08-13 21:04 ` [PATCH 2/3] malloc: Add THP/madvise support for sbrk Adhemerval Zanella via Libc-alpha
2021-08-13 21:04 ` [PATCH 3/3] malloc: Add arch-specific malloc_verify_thp_pagesize for Linux Adhemerval Zanella via Libc-alpha
2021-08-13 21:37 ` [PATCH 0/3] malloc: improve THP effectiveness Guillaume Morin
2021-08-16 20:55 ` Adhemerval Zanella via Libc-alpha
2021-08-17 4:00 ` Siddhesh Poyarekar via Libc-alpha [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=631f477d-c504-94d5-3141-a58263fde5c5@sourceware.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=guillaume@morinfr.org \
--cc=nmanthey@conp-solutions.com \
--cc=siddhesh@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).