From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC][patch] Make DCACHE_LINE runtime-settable
Date: Tue, 26 Jul 2011 02:55:00 -0000 [thread overview]
Message-ID: <20110726002740.GA10655@host1.jankratochvil.net> (raw)
In-Reply-To: <CALoOobNJwUW27ByDjC1JD3B90b8B270=C-U70WHtNSDKUKfXPQ@mail.gmail.com>
On Mon, 25 Jul 2011 22:21:18 +0200, Paul Pluzhnikov wrote:
> On Mon, Jul 25, 2011 at 12:00 PM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> > I have seen some of the target_read_memory requests are needlessly fragmented
> > into LINE_SIZE_POWER sized read requests. Â Have you considered making the
> > gdbserver protocol read requests size dynamic depending on the caller's
> > requested read size?
>
> Uhm. The caller read request size here is 8 bytes (else I didn't
> understand what you are suggesting):
I was rechecking now the problem of consecutive small reads:
Sending packet: $m152bfc0,4#c0...Packet received: 2f757372
Sending packet: $m152bfc4,4#c4...Packet received: 2f6c6962
Sending packet: $m152bfc8,4#c8...Packet received: 36342f72
Sending packet: $m152bfcc,4#f3...Packet received: 65646c61
and they come from target_read_string - which you already solve in the other
thread. I had wrong expectation they come from large memory transfer
requests.
Thanks,
Jan
prev parent reply other threads:[~2011-07-26 0:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 2:40 Paul Pluzhnikov
2011-07-23 16:57 ` Eli Zaretskii
2011-07-25 15:01 ` Tom Tromey
2011-07-25 18:47 ` Paul Pluzhnikov
2011-07-25 19:22 ` Tom Tromey
2011-07-25 19:32 ` Pedro Alves
2011-07-25 19:33 ` Tom Tromey
2011-07-25 20:49 ` Pedro Alves
2011-07-25 20:22 ` Eli Zaretskii
2011-07-25 21:04 ` Paul Pluzhnikov
2011-07-26 0:28 ` Pedro Alves
2011-07-26 9:51 ` Eli Zaretskii
2011-07-25 19:26 ` Jan Kratochvil
2011-07-25 20:58 ` Paul Pluzhnikov
2011-07-26 2:55 ` Jan Kratochvil [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=20110726002740.GA10655@host1.jankratochvil.net \
--to=jan.kratochvil@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