From: Grant Edwards <grante@visi.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Momchil Velikov <velco@fadata.bg>, gdb-patches@sources.redhat.com
Subject: Re: RDI code busy-waiting on running target?
Date: Mon, 15 Jul 2002 10:59:00 -0000 [thread overview]
Message-ID: <20020715125032.A19565@visi.com> (raw)
In-Reply-To: <3D32F8DB.30803@ges.redhat.com>; from ac131313@ges.redhat.com on Mon, Jul 15, 2002 at 12:31:23PM -0400
On Mon, Jul 15, 2002 at 12:31:23PM -0400, Andrew Cagney wrote:
>
> >> If it is a timeout, it should be waiting for min (time until next
> >> timeout, gui keep alive delta).
> >
> > Sorry, I've no idea what that means. Care to explain?
[...]
> The code appears to be implementing a timer using polling.
The command-line UI or Insight? (Are there any other linked-in
UIs?)
> Something somewhere must know the intended timer frequency and
> hence the sleep should be the minimum of:
>
> - time to next timer event
> - frequency that gui wants control
Doh! Now I see. I completely missed that the min ([...], [...])
was pseudo-code. What do other targets do? (I should go
look.) 10ms is the minimum practical delay under most of the
Linux or Linux-like OSes that I know about. Longer is easier.
Shorter isn't.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2002-07-15 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020711175854.A29971@visi.com>
2002-07-11 16:53 ` Grant Edwards
2002-07-11 17:28 ` Keith Seitz
2002-07-11 17:44 ` Grant Edwards
2002-07-12 8:24 ` Grant Edwards
2002-07-12 11:04 ` Grant Edwards
2002-07-14 10:04 ` Andrew Cagney
2002-07-14 10:10 ` Momchil Velikov
2002-07-14 11:28 ` Andrew Cagney
2002-07-15 0:28 ` Grant Edwards
2002-07-15 9:42 ` Andrew Cagney
2002-07-15 10:59 ` Grant Edwards [this message]
2002-07-11 19:08 Dan Kegel
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=20020715125032.A19565@visi.com \
--to=grante@visi.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=velco@fadata.bg \
/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