Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: per-inferior register cache for gdbserver
Date: Wed, 24 Apr 2002 16:31:00 -0000	[thread overview]
Message-ID: <3CC73D58.2F9D2CF@redhat.com> (raw)
In-Reply-To: <20020420145943.A25321@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> On Sat, Apr 20, 2002 at 02:48:49PM -0400, Andrew Cagney wrote:
> > >Moving right along.  This is the initial per-inferior register cache
> > >interface; in my development sources (which are almost ready for
> > >submittal) the interface is actually somewhat different, but that's
> > >entangled with the rest of threading right now.  I'll be extracting it in
> > >the next few days.
> > >
> > >So, this patch is a step on the road, but don't get too attached to the
> > >interface.  It'll be much nicer, I promise.  This version works as-is,
> > >which
> > >I can't say for the nicer one at the moment.
> >
> > Um, would there be more benefit in getting this sort of thing
> > implemented in the core of GDB?  I just don't see a per-lwp cache in the
> > remote target making much difference to GDB's thread debugging performance.
> 
> There would be more benefit in doing it in GDB, certainly.  But like a
> lot of optimizations I'm doing in the server right now, this is
> beneficial to the server itself.  Note that I completely replaced the
> global cache; I switch back and forth amongst LWPs during operations,
> sometimes.  It simplifies life in the server greatly if I can just say
> "give me this thread's current registers" and let the register cache
> handle the details.
> 
> In GDB, this would be a performance optimization; in the server it's
> there for simplicity more than anything else.  It also lets me delay
> register fetching for other threads until it's actually needed, which
> it may never be (in the next version of the cache, which has valid
> flags).  I can get numbers later on how many register fetches it
> actually saves; I suspect it's fairly small.

For what it's worth, I explored a lot of things like this
(including exactly this, I think), when I was re-writing
procfs.c.  In the end, they resulted in no measurable performance
improvement at all.   ;-|

But I had fun playing around with them, of course...

Michael


      parent reply	other threads:[~2002-04-24 23:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20 10:22 Daniel Jacobowitz
2002-04-20 11:48 ` Andrew Cagney
2002-04-20 11:59   ` Daniel Jacobowitz
2002-04-20 18:23     ` Andrew Cagney
2002-06-13 12:29       ` Daniel Jacobowitz
2002-04-24 16:31     ` Michael Snyder [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=3CC73D58.2F9D2CF@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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