From: "Frank Ch. Eigler" <fche@redhat.com>
To: Milian Wolff <mail@milianw.de>
Cc: elfutils-devel@sourceware.org
Subject: Re: parallel downloads of multiple debuginfo files
Date: Fri, 8 Apr 2022 17:31:20 -0400 [thread overview]
Message-ID: <20220408213120.GE23295@redhat.com> (raw)
In-Reply-To: <10231549.TdVgQxHH2d@milian-workstation>
Hi -
> But once again - isn't this a problem that everyone using dwfl is going to
> encounter? Should we not try to find a general solution to this problem and
> fix it for all consumers of the API?
I suspect not many apps are going to have a complete list of files
they know they'll need a priori. A live profiler tends to find out
about target files gradually. A debugger uses debuginfo to help
enumerate other debuginfo. DWZ files can only be even known of when
the base DWARF file is fetched. So yeah I'm not sure there exists a
widespread general problem for which multithreading is not a workable
solution.
- FChE
next prev parent reply other threads:[~2022-04-08 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 20:53 Milian Wolff
2022-04-08 20:54 ` Frank Ch. Eigler
2022-04-08 20:58 ` Milian Wolff
2022-04-08 21:31 ` Frank Ch. Eigler [this message]
2022-04-15 13:11 ` 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=20220408213120.GE23295@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mail@milianw.de \
/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).