public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: systemtap@sources.redhat.com
Subject: Re: [Forw:] Re: Slowness module generating for testsuite/systemtap.stress/current.stp  due to elfutils-0.131
Date: Fri, 08 Feb 2008 21:17:00 -0000	[thread overview]
Message-ID: <20080208211626.DB82E2701AA@magilla.localdomain> (raw)
In-Reply-To: Frank Ch. Eigler's message of  Friday, 8 February 2008 09:12:02 -0500 <y0mzlub4jwt.fsf@ton.toronto.redhat.com>

Sorry, I'm far too backlogged to look into this directly any time soon.
I can give you a few suggestions off hand on how to investigate.

First thing is to verify that libdwfl alone has slowed down, ruling out
some bizarre interaction with systemtap's particular use.  Compare
loc2c-test -K or some other elfutils test program between the two builds.
The -K option (or -K`uname -r`) translates to the same libdwfl reporting
functions that systemtap uses.  

Next, I'd check for any big difference in system calls.  If strace -c
output differs a great deal, then take traces to see if the new one is
opening a much larger number of files or something like that.

If all that is the same, the reporting pass is not the culprit.
The next thing that comes to mind is the new relocation behavior.
This is the feature added in 0.131 to facilitate the markers work
in .ko modules.  If you call dwfl_module_getelf then it eagerly
applies relocs to all sections in case you are going to get their
contents via libelf calls.  Perhaps we are getting too many relocs
eagerly applied and that is unexpectedly costly.  Or perhaps there 
is some bug causing the reloc work to be repeated many times or 
something like that.  In the debugger, look at the number of calls
to __libdwfl_relocate and __libdwfl_relocate_section.


Thanks,
Roland

      parent reply	other threads:[~2008-02-08 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 13:20 William Cohen
     [not found] ` <y0mzlub4jwt.fsf@ton.toronto.redhat.com>
2008-02-08 21:17   ` Roland McGrath [this message]

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=20080208211626.DB82E2701AA@magilla.localdomain \
    --to=roland@redhat.com \
    --cc=systemtap@sources.redhat.com \
    /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).