public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "toolybird at tuta dot io" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/30723] Repeated posix_memalign calls produce long free lists, high fragmentation
Date: Fri, 11 Aug 2023 06:11:40 +0000	[thread overview]
Message-ID: <bug-30723-131-KUkK7wY5EG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30723-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30723

--- Comment #3 from Toolybird <toolybird at tuta dot io> ---
Latest patch [1] on top of the previous one appears to have done the trick.
Thanks so much for all your efforts. We will get this out to users once it hits
the tree (and hopefully the 2.38 branch).

[1]
https://inbox.sourceware.org/libc-alpha/87pm3uajev.fsf@oldenburg.str.redhat.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-11  6:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  2:37 [Bug malloc/30723] New: posix_memalign performance regression toolybird at tuta dot io
2023-08-05  3:02 ` [Bug malloc/30723] posix_memalign performance regression in glibc-2.38 (since 24cdd6c71debfd10a9f7cb217fe2a2c4c486ed6f?) sam at gentoo dot org
2023-08-05  3:04 ` sam at gentoo dot org
2023-08-05 13:13 ` freswa at archlinux dot org
2023-08-05 21:54 ` dilfridge at gentoo dot org
2023-08-06 18:23 ` kocelfc at tutanota dot com
2023-08-09 18:54 ` [Bug malloc/30723] Repeated calls posix_memalign calls produce long free lists, high fragmentation fweimer at redhat dot com
2023-08-09 19:37 ` [Bug malloc/30723] Repeated " fweimer at redhat dot com
2023-08-10  5:45 ` toolybird at tuta dot io
2023-08-11  6:11 ` toolybird at tuta dot io [this message]
2023-08-11  9:24 ` fweimer at redhat dot com
2023-08-15  6:25 ` fweimer at redhat dot com
2023-09-11  8:02 ` [Bug malloc/30723] Poor posix_memalign performance with long free lists fweimer at redhat dot com
2023-09-11  8:03 ` fweimer at redhat dot com

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=bug-30723-131-KUkK7wY5EG@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).