From: Tom Tromey <tromey@redhat.com>
To: ppluzhnikov@google.com (Paul Pluzhnikov)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Make target_read_string faster over high-latency links.
Date: Mon, 18 Jul 2011 18:06:00 -0000 [thread overview]
Message-ID: <m3k4bf7byo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110715180748.A0390190BC2@elbrus2.mtv.corp.google.com> (Paul Pluzhnikov's message of "Fri, 15 Jul 2011 11:07:48 -0700 (PDT)")
>>>>> "Paul" == Paul Pluzhnikov <ppluzhnikov@google.com> writes:
Paul> 1. is it ok to read strings 128 bytes at a time, or are there
Paul> scenarios (JTAG?) where the latency is low but throughput is also
Paul> low (and so reading "unnecessary" data is expensive) ?
I don't know, but I assume so.
Paul> 1a. If yes, would it be acceptable to make this size a
Paul> runtime-configurable parameter?
Yes.
Paul> 2. Current target_read_string aligns reads on a 4-byte boundary. Code
Paul> could be simplified quite a bit if it didn't do that.
Paul> Are there targets where such alignment is required?
I don't know this either, sorry.
What about making it possible for gdbserver to do the string-reading
itself, with a fallback to the existing code for older versions? Then
you don't need a parameter or any tuning.
Tom
next prev parent reply other threads:[~2011-07-18 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 18:09 Paul Pluzhnikov
2011-07-18 18:06 ` Tom Tromey [this message]
2011-07-18 19:01 ` Paul Pluzhnikov
2011-07-19 17:44 ` Paul Pluzhnikov
2011-07-19 17:52 ` Tom Tromey
2011-07-22 16:53 ` Joel Brobecker
2011-07-22 17:01 ` Paul Pluzhnikov
2011-07-25 14:42 ` Daniel Jacobowitz
2011-07-26 11:15 ` Jan Kratochvil
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=m3k4bf7byo.fsf@fleche.redhat.com \
--to=tromey@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