From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v5 1/1] memalign: Support scanning for aligned chunks.
Date: Thu, 13 Apr 2023 07:46:33 -0300 [thread overview]
Message-ID: <1f0cec64-320d-199a-b455-9155ef37346c@linaro.org> (raw)
In-Reply-To: <xn7cugy25r.fsf@greed.delorie.com>
On 12/04/23 22:57, DJ Delorie wrote:
> Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:
>> Yes and with malloc/tst-malloc-thread-fail-malloc-hugetlb1 as well. But
>> the hugetlb1 and hugetlb2 just essentially enable hugepages with extra
>> mprotect/madvise calls. I don't think they play a role in this issue
>> (they won't affect any metadata setting, just the timings on the tests).
>
> I still can't reproduce this; how much free memory is on that machine?
About 64GB:
$ free
total used free shared buff/cache available
Mem: 65760296 6847324 41000244 17540 17912728 58182972
Swap: 8388604 0 8388604
> Have you tested this particular setup without my patch? I inspected all
> the tcache code changes and didn't find anything...
>
I will check this patch, thanks.
next prev parent reply other threads:[~2023-04-13 10:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 3:58 [PATCH v1 " DJ Delorie
2022-07-19 2:54 ` Carlos O'Donell
2022-07-19 3:57 ` [PATCH v2 " DJ Delorie
2022-07-19 9:19 ` Florian Weimer
2022-07-19 17:32 ` DJ Delorie
2022-07-20 0:32 ` [PATCH v3 " DJ Delorie
2022-07-22 20:21 ` DJ Delorie
2022-07-22 20:28 ` Joseph Myers
2022-07-28 19:50 ` [PATCH v4 " DJ Delorie
2022-08-17 19:00 ` DJ Delorie
2022-11-10 21:40 ` Ping^2: " DJ Delorie
2023-03-20 21:49 ` Ping^3: " DJ Delorie
2023-03-28 19:07 ` Adhemerval Zanella Netto
2023-03-29 4:20 ` [PATCH v5 " DJ Delorie
2023-03-29 19:41 ` Adhemerval Zanella Netto
2023-03-29 20:36 ` DJ Delorie
2023-03-30 10:04 ` Cristian Rodríguez
2023-03-30 10:50 ` Adhemerval Zanella Netto
2023-03-30 21:43 ` Cristian Rodríguez
2023-04-12 17:04 ` Xi Ruoyao
2023-04-12 17:16 ` DJ Delorie
2023-04-12 17:26 ` Xi Ruoyao
2023-04-13 1:52 ` [PATCH v6 " DJ Delorie
2023-04-13 5:51 ` Xi Ruoyao
2023-04-17 21:48 ` Carlos O'Donell
2023-04-18 1:25 ` [PATCH v7] " DJ Delorie
2023-04-18 13:58 ` Carlos O'Donell
2023-04-18 15:02 ` DJ Delorie
2023-04-12 17:33 ` [PATCH v5 1/1] " Adhemerval Zanella Netto
2023-04-12 17:40 ` DJ Delorie
2023-04-12 18:01 ` Adhemerval Zanella Netto
2023-04-13 1:57 ` DJ Delorie
2023-04-13 10:46 ` Adhemerval Zanella Netto [this message]
2023-04-05 14:07 ` Stefan Liebler
2023-04-05 17:58 ` DJ Delorie
2023-04-11 11:40 ` Stefan Liebler
2023-04-12 11:23 ` Stefan Liebler
2023-03-31 15:39 ` Adhemerval Zanella Netto
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=1f0cec64-320d-199a-b455-9155ef37346c@linaro.org \
--to=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).