From: Mark Wielaard <mark@klomp.org>
To: Jonathon Anderson <jma14@rice.edu>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH 0/2] libdw: Rewrite the memory handler to be more robust
Date: Tue, 29 Oct 2019 20:17:00 -0000 [thread overview]
Message-ID: <20191029201742.GG2775@wildebeest.org> (raw)
In-Reply-To: <1572375325.2128.1@rice.edu>
Hi Jonathon,
On Tue, Oct 29, 2019 at 01:55:25PM -0500, Jonathon Anderson wrote:
> 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.
Thanks. But it looks like your mail client munged the patches a bit
making it a bit tricky to apply. Could you resent them using git
send-email or do you have some public repo I could get them from?
Thanks,
Mark
next prev parent reply other threads:[~2019-10-29 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 18:55 Jonathon Anderson
2019-10-29 20:17 ` Mark Wielaard [this message]
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=20191029201742.GG2775@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=jma14@rice.edu \
/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).