public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/30303] FAIL: malloc/tst-memalign-2-mcheck Date: Fri, 21 Apr 2023 09:05:29 +0000 [thread overview] Message-ID: <bug-30303-131-o1p3zNZR1Z@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30303-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30303 John David Anglin <danglin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dj at redhat dot com --- Comment #2 from John David Anglin <danglin at gcc dot gnu.org> --- Introduced by following commit: dave@mx3210:~/gnu/glibc/glibc$ git bisect good 24cdd6c71debfd10a9f7cb217fe2a2c4c486ed6f is the first bad commit commit 24cdd6c71debfd10a9f7cb217fe2a2c4c486ed6f Author: DJ Delorie <dj@redhat.com> Date: Wed Mar 29 00:18:40 2023 -0400 memalign: Support scanning for aligned chunks. This patch adds a chunk scanning algorithm to the _int_memalign code path that reduces heap fragmentation by reusing already aligned chunks instead of always looking for chunks of larger sizes and splitting them. The tcache macros are extended to allow removing a chunk from the middle of the list. The goal is to fix the pathological use cases where heaps grow continuously in workloads that are heavy users of memalign. Note that tst-memalign-2 checks for tcache operation, which malloc-check bypasses. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> malloc/Makefile | 3 +- malloc/malloc.c | 260 +++++++++++++++++++++++++++++++++++++++++++----- malloc/tst-memalign-2.c | 155 +++++++++++++++++++++++++++++ 3 files changed, 390 insertions(+), 28 deletions(-) create mode 100644 malloc/tst-memalign-2.c -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-21 9:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-01 19:10 [Bug malloc/30303] New: " danglin at gcc dot gnu.org 2023-04-01 19:12 ` [Bug malloc/30303] " danglin at gcc dot gnu.org 2023-04-21 9:05 ` danglin at gcc dot gnu.org [this message] 2023-04-21 16:57 ` dj at redhat dot com 2023-04-21 22:23 ` danglin at gcc dot gnu.org
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-30303-131-o1p3zNZR1Z@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: linkBe 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).