Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jim Blandy" <jimb@red-bean.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: testsuite: Of all the timeouts provided always select the largest
Date: Tue, 26 Feb 2008 16:39:00 -0000	[thread overview]
Message-ID: <8f2776cb0802260824y2c87f942sa925149de3c38cef@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0802261558210.24968@perivale.mips.com>

On Tue, Feb 26, 2008 at 8:09 AM, Maciej W. Rozycki <macro@mips.com> wrote:
>   All the callers would have to be updated and unfortunately the dependency
>  may not necessarily be linear.  For example for a fast target accessed
>  through a slow port the factor for transferring data through, such as
>  downloading a program image, would have to be higher than for a slow
>  target accessed through a fast port.  Contrariwise the factor applied to
>  actions involving execution on the respective systems.  In general I do
>  agree it is a good idea, but that is a lot of work that best be well
>  thought before commencing.

All true, except for the "all callers" part, I think: couldn't
gdb_expect recognize a '-timeout-factor' flag as its first argument?
Then we could update call sites as we came across them.

It's certainly not linear, but linear is better than constant, surely.
 For the sake of setting timeouts, we only need an upper bound.


  reply	other threads:[~2008-02-26 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 15:55 Maciej W. Rozycki
2008-02-26 16:02 ` Jim Blandy
2008-02-26 16:17   ` Maciej W. Rozycki
2008-02-26 16:39     ` Jim Blandy [this message]
2008-02-27 15:43       ` Maciej W. Rozycki
2008-02-27 15:45         ` Daniel Jacobowitz
2008-02-26 16:10 ` 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=8f2776cb0802260824y2c87f942sa925149de3c38cef@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.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