This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RDI code busy-waiting on running target?


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]