From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3817 invoked by alias); 15 Jul 2002 17:46:33 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 3775 invoked from network); 15 Jul 2002 17:46:32 -0000 Received: from unknown (HELO conn.mc.mpls.visi.com) (208.42.156.2) by sources.redhat.com with SMTP; 15 Jul 2002 17:46:32 -0000 Received: from grante.comtrol.com (isis.visi.com [209.98.98.8]) by conn.mc.mpls.visi.com (Postfix) with SMTP id 1A9B58281 for ; Mon, 15 Jul 2002 12:46:32 -0500 (CDT) Received: (qmail 19577 invoked by uid 500); 15 Jul 2002 17:50:33 -0000 Date: Mon, 15 Jul 2002 10:59:00 -0000 From: Grant Edwards To: Andrew Cagney Cc: Momchil Velikov , gdb-patches@sources.redhat.com Subject: Re: RDI code busy-waiting on running target? Message-ID: <20020715125032.A19565@visi.com> References: <20020711175854.A29971@visi.com> <20020711184343.A4472@visi.com> <20020712102650.A6637@visi.com> <20020712130727.A7707@visi.com> <3D31AC1D.5060906@ges.redhat.com> <87ele68cd1.fsf@fadata.bg> <3D31BC77.5020700@ges.redhat.com> <20020714225500.A1054@grante.dsl.visi.com> <3D32F8DB.30803@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3D32F8DB.30803@ges.redhat.com>; from ac131313@ges.redhat.com on Mon, Jul 15, 2002 at 12:31:23PM -0400 X-SW-Source: 2002-07/txt/msg00329.txt.bz2 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