Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Luis Machado <lgustavo@codesourcery.com>
Subject: Re: [RFC][patch] Avoid repeated calls to solib_add on initial attach.
Date: Wed, 20 Jul 2011 16:59:00 -0000	[thread overview]
Message-ID: <CALoOobOnmiG4fnpWohxS6znfrH6VvgmgxB8RDucnChQqEgY8wQ@mail.gmail.com> (raw)
In-Reply-To: <201107201735.13150.pedro@codesourcery.com>

On Wed, Jul 20, 2011 at 9:35 AM, Pedro Alves <pedro@codesourcery.com> wrote:

>>   qStr {addr},{maxlen},{terminator}
...
> We considered a packet like this too, but decided that bumping
> target_read_string first and seeing if anything breaks would be
> better.  Haven't heard back of any breakage or slowdown so far.
> I propose we do the same upstream.

But do you have any targets where reading individual words is slow?

I don't know about any such targets first-hand, but I've heard that
JTAG reading could be exceedingly slow.

Another possible alternative is to make this a run-time parameter:
'maintenance set string-read-size 64' or some such. Default to 64 and
let JTAG people dial it down if it ever becomes a problem for them?

Thanks for your comments.

-- 
Paul Pluzhnikov


  reply	other threads:[~2011-07-20 16:45 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
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 [this message]
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=CALoOobOnmiG4fnpWohxS6znfrH6VvgmgxB8RDucnChQqEgY8wQ@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    --cc=pedro@codesourcery.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