From: Gary Benson <gbenson@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC][patch] Avoid repeated calls to solib_add on initial attach.
Date: Wed, 20 Jul 2011 13:56:00 -0000 [thread overview]
Message-ID: <20110720131705.GA32570@redhat.com> (raw)
In-Reply-To: <20110715205209.8B3B3190BC2@elbrus2.mtv.corp.google.com>
Paul Pluzhnikov wrote:
> Following up on my earlier "slow on high-latency links" message:
> http://sourceware.org/ml/gdb-patches/2011-07/msg00391.html ...
>
> Attached patch avoids calling solib_add twice when initially attaching
> inferior.
>
> I am not entirely happy about this patch, but don't have a better
> idea for a fix, and do want to avoid repeated rescans of the shared
> library list.
>
> (Some of our executables use 4000+ shared libraries, and the time in
> solib_add does add up.)
>
> Tested on Linux/x86_64, no regressions.
>
> Comments?
I've had a look at this and aside from the typo noted below it seems
fine. I didn't see any speedup on the 1000 library testcase I've been
using for my own stuff (the bulk of the time seemed to be printing all
the "Loaded symbols for X.so" and "Reading symbols from X.so"
messages) but maybe this is because I'm running everything locally and
possibly you are not? In any event, the second solib_add call was
skipped as expected.
> made all the inferior hook methods consistent, this call could be
> removed. Call it only after the solib target has been initialized by
> - solib_create_inferior_hook. */
> + solib_create_inferior_hook. Only do this if not alreay done from
^^^^^^
Typo
Cheers,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2011-07-20 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 20:58 Paul Pluzhnikov
2011-07-20 13:56 ` Gary Benson [this message]
2011-07-20 14:59 ` Pedro Alves
2011-07-20 16:15 ` Paul Pluzhnikov
2011-07-20 16:56 ` Pedro Alves
2011-07-20 16:59 ` Paul Pluzhnikov
2011-07-20 17:36 ` Pedro Alves
2011-07-20 18:38 ` Pedro Alves
2011-07-22 17:27 ` Paul Pluzhnikov
2011-07-22 17:51 ` Pedro Alves
2011-07-22 17:36 ` Tom Tromey
2011-07-22 17:43 ` Pedro Alves
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=20110720131705.GA32570@redhat.com \
--to=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.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