public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org, DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH v2 0/2] Improve MAP_HUGETLB with glibc.malloc.hugetlb=2
Date: Fri, 24 Nov 2023 15:57:04 +0800	[thread overview]
Message-ID: <CABQgh9F9NgFGMDS5o5iXAuwSLEHx6DhS_VDC27-EgwkJA0F=aQ@mail.gmail.com> (raw)
In-Reply-To: <20231123172915.893408-1-adhemerval.zanella@linaro.org>

On Fri, 24 Nov 2023 at 01:29, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
>
> On some tests with glibc.malloc.hugetlb=2, there are some allocation
> patterns that are not backed up by large pages (different than
> libhugetlfs morecore implementation).
>
> Adhemerval Zanella (2):
>   elf: Add a way to check if tunable is set (BZ 27069)
>   malloc: Improve MAP_HUGETLB with glibc.malloc.hugetlb=2

Thanks, Adhemerval

Tested on aarch64, based on glibc master branch.
With these two patches, our application using 2M pages does not
trigger page faults now,
and many page faults before.

Tested-by: Zhangfei Gao <zhangfei.gao@linaro.org>

      parent reply	other threads:[~2023-11-24  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 17:29 Adhemerval Zanella
2023-11-23 17:29 ` [PATCH v2 1/2] elf: Add a way to check if tunable is set (BZ 27069) Adhemerval Zanella
2023-11-28 21:38   ` DJ Delorie
2023-11-29 12:29     ` Adhemerval Zanella Netto
2023-11-23 17:29 ` [PATCH v2 2/2] malloc: Improve MAP_HUGETLB with glibc.malloc.hugetlb=2 Adhemerval Zanella
2023-11-28 21:43   ` DJ Delorie
2023-11-24  7:57 ` Zhangfei Gao [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABQgh9F9NgFGMDS5o5iXAuwSLEHx6DhS_VDC27-EgwkJA0F=aQ@mail.gmail.com' \
    --to=zhangfei.gao@linaro.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=dj@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).