From: Jonathon Anderson <jma14@rice.edu>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: [PATCH 0/2] libdw: Rewrite the memory handler to be more robust
Date: Tue, 29 Oct 2019 18:55:00 -0000 [thread overview]
Message-ID: <1572375325.2128.1@rice.edu> (raw)
Hello,
This is (revived and rebased) version of the libdw memory manager that
isn't affected by the PTHREAD_KEYS_MAX limit. There are some downsides,
in particular if an application spawns many short-lived threads that
all touch a Dwarf (enough to cause an allocation), there's about ~8N
bytes of memory overhead.
The first patch is not required and adds some configure-time options
for Valgrind annotation support (although, I'm not a serious autotools
user, so it might need some work).
-Jonathon
----------------------------------------------------------------
Jonathon Anderson (2):
Add configure options for Valgrind annotations.
libdw: Rewrite the memory handler to be more robust.
ChangeLog | 5 +++++
configure.ac | 30 ++++++++++++++++++++++++++++++
lib/atomics.h | 2 ++
libdw/ChangeLog | 9 +++++++++
libdw/dwarf_begin_elf.c | 7 ++++---
libdw/dwarf_end.c | 24 +++++++++++++-----------
libdw/libdwP.h | 67
++++++++++++++++++++++++++++++++-----------------------------------
libdw/libdw_alloc.c | 69
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
8 files changed, 160 insertions(+), 53 deletions(-)
next reply other threads:[~2019-10-29 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 18:55 Jonathon Anderson [this message]
2019-10-29 20:17 ` Mark Wielaard
2019-10-29 20:22 ` Jonathon Anderson
2019-10-29 21:15 ` [PATCH 1/2] Add configure options for Valgrind annotations Mark Wielaard
2019-10-29 21:15 ` [PATCH 2/2] libdw: Rewrite the memory handler to be more robust Mark Wielaard
2019-11-07 17:20 ` Mark Wielaard
2019-11-07 18:13 ` Jonathon Anderson
2019-11-08 16:22 ` Mark Wielaard
2019-11-07 18:40 ` Jonathon Anderson
2019-11-08 16:22 ` Mark Wielaard
2019-11-08 17:41 ` Jonathon Anderson
2019-11-07 17:19 ` [PATCH 1/2] Add configure options for Valgrind annotations Mark Wielaard
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=1572375325.2128.1@rice.edu \
--to=jma14@rice.edu \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).