From: "Zack Weinberg" <zack@owlfolio.org>
To: "DJ Delorie" <dj@redhat.com>, "Florian Weimer" <fweimer@redhat.com>
Cc: "GNU libc development" <libc-alpha@sourceware.org>, toolybird@tuta.io
Subject: Re: [PATCH] malloc: Enable merging of remainders in memalign (bug 30723)
Date: Wed, 09 Aug 2023 18:20:31 -0400 [thread overview]
Message-ID: <04c5dca3-4e3c-4e46-a13f-e402637c15f3@app.fastmail.com> (raw)
In-Reply-To: <xna5uzq3mm.fsf@greed.delorie.com>
On Wed, Aug 9, 2023, at 5:58 PM, DJ Delorie via Libc-alpha wrote:
> I would note that everything else malloc does has this problem, too.
> Without limits or checks on fastbin size, anything that puts a chunk
> on the fastbin could "permanently" block consolidation somewhere.
This might also be a change you would only feel comfortable making if we
had a more robust test/bench suite, but could we have a more aggressive
consolidation pass, capable of pulling stuff back out of the fastbins,
that was triggered at least some fraction of the times we think we need
to expand the heap?
zw
next prev parent reply other threads:[~2023-08-09 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 18:51 Florian Weimer
2023-08-09 21:58 ` DJ Delorie
2023-08-09 22:20 ` Zack Weinberg [this message]
2023-08-09 23:10 ` DJ Delorie
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=04c5dca3-4e3c-4e46-a13f-e402637c15f3@app.fastmail.com \
--to=zack@owlfolio.org \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=toolybird@tuta.io \
/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).