Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Paul_Koning@dell.com, gdb@sourceware.org,
	gdb-patches@sourceware.org, pedro@codesourcery.com
Subject: Re: [remote protocol] support for disabling packet acknowledgement
Date: Sat, 26 Jul 2008 05:54:00 -0000	[thread overview]
Message-ID: <ufxpxyyup.fsf@gnu.org> (raw)
In-Reply-To: <4889DF56.6070406@codesourcery.com>

> Date: Fri, 25 Jul 2008 10:12:38 -0400
> From: Sandra Loosemore <sandra@codesourcery.com>
> CC:  Paul_Koning@dell.com,  gdb@sourceware.org,   gdb-patches@sourceware.org,  pedro@codesourcery.com
> 
> >> You'll note the documentation says turning off acks may be desirable to reduce 
> >> communication overhead *or* "for other reasons".  In fact, it is the "other 
> >> reasons" that motivated this patch.  We are working on designing the extensions 
> >> to the remote protocol to support nonstop mode, and we realized that we simply 
> >> cannot do it in combination with using +/- acks on the asynchronous responses.
> > 
> > Then please just say so in the docs.
> 
> As you'll note from subsequent discussion, we decided to use another mechanism 
> for non-stop mode, so it has no dependence on the noack mode patch any more. 
> I'm not sure what else you think the docs for noack mode should say?

Perhaps nothing, now that the decision was to abandon the original
approach.  But the principle remains: if there's some _real_ reason to
including a feature in GDB, let's state that reason in the docs,
instead of hiding it in some "etc."

> Incidentally, I am working on docs for non-stop mode now -- both the user-level 
> changes, and the remote protocol pieces.

Thanks!


  reply	other threads:[~2008-07-26  5: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
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 [this message]
  -- 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=ufxpxyyup.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Paul_Koning@dell.com \
    --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