Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Koning <Paul_Koning@dell.com>
To: pedro@codesourcery.com
Cc: gdb@sourceware.org,     drow@false.org,
	    sandra@codesourcery.com,     gdb-patches@sourceware.org
Subject: Re: [remote protocol] support for disabling packet acknowledgement
Date: Fri, 11 Jul 2008 18:54:00 -0000	[thread overview]
Message-ID: <18551.44113.66097.903273@djudge-us-nas.equallogic.com> (raw)
In-Reply-To: <200807111859.02058.pedro@codesourcery.com>

>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

 Pedro> A Friday 11 July 2008 16:53:46, Paul Koning wrote:
 >> >>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
 Daniel> On Fri, Jul 11, 2008 at 04:10:47PM +0100, Pedro Alves wrote:
 >> Agreed.  Telnet to a terminal server that feeds a UART based
 >> target stub is common practice.

 Pedro> Ack, we're all in sync.

 >> TCP at both ends with datagrams in between is too weird to
 >> consider.

 Pedro> Not weird at all, and it is safe.  It doesn't matter what you
 Pedro> have in the middle as long as both ends have tcp.

You're probably thinking about end to end TCP over a datagram cloud.
That works, of course, that's the Internet.  I was talking about TCP
from A to B, raw UART B to C, TCP from C to D.  TCP wouldn't be
helping you detect or correct data loss on the B to C path, and that
means you'd need application layer acks (as in the current remote GDB
protocol) for that case.  But that's a topology that makes no sense to
me and I wouldn't expect ever to see.

   paul


  reply	other threads:[~2008-07-11 18:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 18:59 Sandra Loosemore
2008-07-10 19:09 ` Paul Koning
2008-07-10 19:59   ` Sandra Loosemore
2008-07-10 20:13     ` Paul Koning
2008-07-10 22:33       ` Daniel Jacobowitz
2008-07-11  0:22         ` Sandra Loosemore
2008-07-11  0:43           ` Daniel Jacobowitz
2008-07-11 13:43         ` Paul Koning
2008-07-11 14:35           ` Daniel Jacobowitz
     [not found]       ` <20080710223312.GA19058__14539.8706700236$1215729298$gmane$org@caradoc.them.org>
2008-07-11  3:05         ` Frank Ch. Eigler
2008-07-11  3:25           ` Daniel Jacobowitz
2008-07-11 15:11       ` Pedro Alves
2008-07-11 15:24         ` Daniel Jacobowitz
2008-07-11 15:54           ` Paul Koning
2008-07-11 17:59             ` Pedro Alves
2008-07-11 18:54               ` Paul Koning [this message]
2008-07-11 19:10                 ` Pedro Alves
2008-07-25 13:41 ` Eli Zaretskii
2008-07-25 14:14   ` Sandra Loosemore
2008-07-26  5:54     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2008-07-10 17:23 Pedro Alves
2008-07-10 18:44 ` Paul Koning
2008-07-10 19:08   ` Daniel Jacobowitz
2008-07-25 13:39 ` Eli Zaretskii
2008-08-11 19:40 ` 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=18551.44113.66097.903273@djudge-us-nas.equallogic.com \
    --to=paul_koning@dell.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=sandra@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