From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH] realloc: Return unchanged if request is within usable size
Date: Fri, 25 Nov 2022 15:09:48 -0500 [thread overview]
Message-ID: <20221125200948.2399996-1-siddhesh@sourceware.org> (raw)
If there is enough space in the chunk to satisfy the new size, return
the old pointer as is, thus avoiding any locks or reallocations. The
only real place this has a benefit is in large chunks that tend to get
satisfied with mmap, since there is a large enough spare size (up to a
page) for it to matter. For allocations on heap, the extra size is
typically barely a few bytes (up to 15) and it's unlikely that it would
make much difference in performance.
Also added a smoke test to ensure that the old pointer is returned
unchanged if the new size to realloc is within usable size of the old
pointer.
Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
---
malloc/malloc.c | 6 ++++++
malloc/tst-realloc.c | 21 +++++++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/malloc/malloc.c b/malloc/malloc.c
index 2a61c8b5ee..3ef61bef34 100644
--- a/malloc/malloc.c
+++ b/malloc/malloc.c
@@ -1100,6 +1100,8 @@ static void munmap_chunk(mchunkptr p);
static mchunkptr mremap_chunk(mchunkptr p, size_t new_size);
#endif
+static size_t musable (void *mem);
+
/* ------------------ MMAP support ------------------ */
@@ -3396,6 +3398,10 @@ __libc_realloc (void *oldmem, size_t bytes)
if (__glibc_unlikely (mtag_enabled))
*(volatile char*) oldmem;
+ /* If there's usable space in the current chunk, return as is. */
+ if (bytes <= musable (oldmem))
+ return oldmem;
+
/* chunk corresponding to oldmem */
const mchunkptr oldp = mem2chunk (oldmem);
/* its size */
diff --git a/malloc/tst-realloc.c b/malloc/tst-realloc.c
index 5eb62a770f..54dd0dd0b3 100644
--- a/malloc/tst-realloc.c
+++ b/malloc/tst-realloc.c
@@ -142,6 +142,27 @@ do_test (void)
free (p);
+ /* Smoke test to make sure that allocations do not move if they have enough
+ space to expand in the chunk. */
+ for (size_t sz = 3; sz < 256 * 1024; sz += 2048)
+ {
+ p = realloc (NULL, sz);
+ if (p == NULL)
+ FAIL_EXIT1 ("realloc (NULL, 31) returned NULL.");
+ size_t newsz = malloc_usable_size (p);
+ printf ("size: %zu, usable size: %zu, extra: %zu\n",
+ sz, newsz, newsz - sz);
+ void *new_p = realloc (p, newsz);
+ if (new_p != p)
+ FAIL_EXIT1 ("Expanding (%zu bytes) to usable size (%zu) moved block",
+ sz, newsz);
+ free (new_p);
+
+ /* We encountered a large enough extra size at least once. */
+ if (newsz - sz > 1024)
+ break;
+ }
+
return 0;
}
--
2.38.1
next reply other threads:[~2022-11-25 20:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 20:09 Siddhesh Poyarekar [this message]
2022-11-25 20:40 ` Andreas Schwab
2022-11-28 14:23 ` Siddhesh Poyarekar
2022-11-28 14:29 ` Andreas Schwab
2022-11-28 17:26 ` [PATCH v2] " Siddhesh Poyarekar
2022-12-06 22:33 ` DJ Delorie
2022-11-28 9:22 [PATCH] " Wilco Dijkstra
2022-11-28 14:13 ` Siddhesh Poyarekar
2022-12-06 12:45 ` Wilco Dijkstra
2022-12-06 18:41 ` Siddhesh Poyarekar
2023-07-03 22:02 ` Aurelien Jarno
2023-07-04 11:17 ` Siddhesh Poyarekar
2023-07-04 16:08 ` Aurelien Jarno
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=20221125200948.2399996-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--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).