From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro@codesourcery.com>
Subject: Re: [PATCH] Speed up target_read_string
Date: Sat, 20 Aug 2011 18:37:00 -0000 [thread overview]
Message-ID: <20110820183702.GA4876@host1.jankratochvil.net> (raw)
In-Reply-To: <4E4E9926.9000800@codesourcery.com>
On Fri, 19 Aug 2011 19:11:02 +0200, Luis Machado wrote:
> The following change is aimed at increasing the performance of
> target_read_string for remote debugging. To accomplish that, the
> buffer has been increased to 64 bytes and we now use
> target_read_partial instead of target_read_memory.
As this is implementation of
[RFC] Make target_read_string faster over high-latency links.
http://sourceware.org/ml/gdb-patches/2011-07/msg00391.html
where Daniel had concerns about some embedded targets without a reply I guess
you are aware of these issues (I am not).
Thanks,
Jan
next prev parent reply other threads:[~2011-08-20 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 17:11 Luis Machado
2011-08-20 18:37 ` Jan Kratochvil [this message]
2011-08-20 21:11 ` Daniel Jacobowitz
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=20110820183702.GA4876@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.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