Date:	Tue, 2 May 2000 13:17:14 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: 3rd Try: Maybe an asm problem? (Problems linking)
In-Reply-To:	<tporgssmgg61b211mceguh69hb1m2pdcum@4ax.com>
Message-ID:	<Pine.SUN.3.91.1000502131643.21668G-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 1 May 2000, Damian Yerrick wrote:

> Oh, BTW, how often should __dpmi_yield() be called, to balance time
> between drawing an app's graphics and giving time to other apps?

It's up to you; it depends on how much does the application need to
draw in the background.  It also depends on the CPU and the other
applications running around.

In Emacs, these aspects are left to the user, by providing a set of
customizable variables.  For example, when Emacs colorizes the buffer
during idle time, the user can determine how many lines will it
colorize before returning to the idle code (which immediately calls
__dpmi_yield), and how much time will it wait until the next chunk of
colorizing.

The usual rule of thumb is to tune the relevant parameters so that
such background operation takes less than 10% of the CPU resources.

- Raw text -