From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Kevin Buettner <kevinb@cygnus.com>,
Kimball Thurston <kimball@sgrail.com>,
gdb@sources.redhat.com
Subject: Re: gdb and dlopen
Date: Thu, 08 Nov 2001 16:17:00 -0000 [thread overview]
Message-ID: <3BF991B1.50205@cygnus.com> (raw)
In-Reply-To: <20011119163624.A25053@nevyn.them.org>
>
> I'm absolutely sure. Or at least, I was... when I tested this, it was
> an obvious win. Now it is an obvious LOSS to turn on the cache. I'm
> not sure why, so I'll have to investigate it later. In 5.0.90-cvs it
> was a win and in current trunk it is a significant performance loss.
>
> This is in the context of a linuxthreads application. We do a
> ridiculous, staggering amount of memory transfer in order to debug a
> linuxthreads application, and parts of it are duplicated.
Hmm, In the context of threads, trying to use the insn/data cache is
cheating :-)
The problem with threads is that GDB is constantly discarding its per
thread information. Only to immediatly turn around and ask that that
same information be re-created. GDB, when switching between threads,
should retain that information in the the ``struct thread_info''. Even
register information could be cached on a per-thread basis.
See
http://sources.redhat.com/gdb/papers/multi-arch/real-multi-arch/index.html#SEC37
enjoy,
Andrew
next prev parent reply other threads:[~2001-11-19 23:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <y3radyrjqf8.wl@paladin.sgrail.com>
2001-10-16 13:15 ` Daniel Jacobowitz
2001-10-16 18:23 ` Kimball Thurston
[not found] ` <20011016213252.A8694@nevyn.them.org>
2001-10-16 19:03 ` Daniel Jacobowitz
2001-10-16 20:04 ` Kimball Thurston
2001-10-16 20:17 ` Andrew Cagney
2001-10-16 22:08 ` Daniel Jacobowitz
2001-10-16 22:19 ` Daniel Jacobowitz
[not found] ` <y3rzo6qx1ej.wl@paladin.sgrail.com>
2001-10-16 22:52 ` Kimball Thurston
2001-10-17 8:07 ` Mark Kettenis
2001-10-17 8:29 ` H . J . Lu
2001-10-17 11:09 ` Daniel Jacobowitz
2001-10-17 14:26 ` Mark Kettenis
2001-10-17 14:34 ` Daniel Jacobowitz
2001-10-17 8:54 ` Andrew Cagney
2001-10-17 15:08 ` Kevin Buettner
2001-10-17 15:57 ` Andrew Cagney
2001-10-17 17:05 ` Daniel Jacobowitz
2001-10-17 23:14 ` Andrew Cagney
2001-10-17 8:42 ` Andrew Cagney
2001-10-17 11:15 ` Daniel Jacobowitz
2001-10-17 12:09 ` Kimball Thurston
2001-10-17 12:58 ` Kevin Buettner
2001-11-08 0:22 ` Daniel Jacobowitz
2001-11-08 8:17 ` Kevin Buettner
2001-11-08 9:44 ` Daniel Jacobowitz
2001-11-08 10:49 ` Kevin Buettner
2001-11-08 11:14 ` Daniel Jacobowitz
2001-11-08 16:17 ` Andrew Cagney [this message]
2001-10-16 22:25 ` Kimball Thurston
2001-10-16 15:05 ` H . J . Lu
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=3BF991B1.50205@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@cygnus.com \
--cc=kimball@sgrail.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