From: Daniel Jacobowitz <drow@false.org>
To: David Anderson <davea@quasar.engr.sgi.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC remove cache thrashing
Date: Tue, 19 Oct 2004 13:20:00 -0000 [thread overview]
Message-ID: <20041018234714.GA26992@nevyn.them.org> (raw)
In-Reply-To: <200410182339.i9INdir2188120@quasar.engr.sgi.com>
On Mon, Oct 18, 2004 at 04:39:44PM -0700, David Anderson wrote:
> gdb has N-squared behavior on getting registers when nptl
> threads on Linux are in use. gdb thrashes the register-cache.
I hadn't replied to your past posts because I didn't have time to
reproduce the problem; last time I checked, it wasn't quadratic. I
don't know what about your setup made the difference, or maybe my
measurements are just out of date.
Fixing this is very easy. I plan to remove the entire mess of affected
code, once I finish renaming thread-db.c, which will hopefully be this
week. We don't need to use thread-db for registers at all.
> Has this multiple-register-cache idea been considered seriously before?
> Is there any proposed outline-of-change?
We need to get rid of all the remaining references to the "current"
registers first. I don't think we're quite there yet.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-10-18 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 2:28 David Anderson
2004-10-19 13:20 ` Daniel Jacobowitz [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=20041018234714.GA26992@nevyn.them.org \
--to=drow@false.org \
--cc=davea@quasar.engr.sgi.com \
--cc=gdb@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