All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Jones <tonyj@suse.de>
To: linux-perf-users@vger.kernel.org
Cc: irogers@google.com
Subject: addr2line performance
Date: Wed, 22 Oct 2025 11:30:21 -0700	[thread overview]
Message-ID: <aPkivW2WoySU1Zkc@suse.de> (raw)

Hi.

https://bugzilla.kernel.org/show_bug.cgi?id=218996#c1 mentions
"there are proposals to move this logic to being from a library again. 
I think the addr2line processing attempted is valiant but ultimately 
using a library will be best" (this was when LLVM addr2line support 
was already present),

Obviously the test patch mentioned in the above bug doesn't address 
the underlying performance issue, only better classifying a timeout 
error.

We have a customer bug complaining about the performance of addr2line.
I'm seeing cases where it's taking over 20 seconds wall clock to 
resolve certain addresses which obviously causes the io_timer to trip 
but the performance of the success path isn't great either.

Obviously BFD isn't an option and (for various reasons) we can't use 
LLVM for this specific distro so I'm looking at the performance
of addr2line.

Can someone point me to the prior "using a library" discussion 
referenced in the above bug or whatever the current thinking is.  I 
couldn't find anything searching the archive.

Thanks in advance!

Tony

-- 
Tony Jones
SUSE Kernel Performance Team

             reply	other threads:[~2025-10-22 18:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 18:30 Tony Jones [this message]
2025-10-29 15:51 ` addr2line performance Ian Rogers
2025-10-31 17:01   ` Tony Jones
2025-10-31 17:49     ` Ian Rogers
2025-10-31 19:39 ` Namhyung Kim
2025-10-31 20:40   ` Tony Jones
2025-11-04  3:16     ` Namhyung Kim

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=aPkivW2WoySU1Zkc@suse.de \
    --to=tonyj@suse.de \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.