From: Jim Blandy <jimb@red-bean.com>
To: gdb@sourceware.org
Subject: Re: to_xfer_partial, qPart, and EOF
Date: Thu, 19 Jan 2006 02:00:00 -0000 [thread overview]
Message-ID: <8f2776cb0601181718ybb52db4pc5c3aca9bf00adfe@mail.gmail.com> (raw)
In-Reply-To: <20060118231837.GA17726@nevyn.them.org>
On 1/18/06, Daniel Jacobowitz <drow@false.org> wrote:
> I'm currently very well aware of the round trip latency in the remote
> protocol; it makes a huge difference over TCP, where larger packets are
> basically free up to a certain size, but round trips are very slow. At
> the time he wanted to pursue this immediately; Andrew wanted to go without
> it for the moment, and it was never revisited.
>
> So that's action item one; I think it's time to add this. So far so good.
This, and a few other remote protocol wrinkles, are consequences of
the mis-layering of the GDB protocol. The protocol should simply
specify that the entire block of data gets transmitted, and let lower
layers handle retransmission and fragmentation.
I recognize it's probably not practical to fix this today, and maybe
it never will be. But I keep running into instances of this when I
work on the remote protocol --- tracepoint definition packets needing
to be broken up into pieces to avoid long packets; breakpoint packets
needing to be idempotent, because they might be retransmitted; and so
on --- so I wanted to mention it. Perhaps someone will have a flash
of super-coder powers some weekend.
> Any comments on either of these plans? Otherwise I will probably implement
> them in the next couple of days. I'm doing a lot of work in this area
> at present.
Sounds great to me.
next prev parent reply other threads:[~2006-01-19 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 23:19 Daniel Jacobowitz
2006-01-19 2:00 ` Jim Blandy [this message]
2006-01-19 2:03 ` 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=8f2776cb0601181718ybb52db4pc5c3aca9bf00adfe@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb@sourceware.org \
/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