public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Maurilio Longo <maurilio.longo@libero.it>
To: linux mailing list <linux-msdos@vger.kernel.org>
Subject: Re: Dosemu and clipper applications eating all CPU
Date: Mon, 15 Mar 2004 12:53:41 +0100	[thread overview]
Message-ID: <40559945.CCB3126A@libero.it> (raw)
In-Reply-To: 40523AA4.8040304@aknet.ru

Stas,

it probably depends on the linker used to create the clipper app, here we use
blinker to create a protect mode application, and this application calls
src/base/async/int.c function ms_dos case 0x2C.

In 1.1.3 (which is the dosemu we use) I had to make the changes I told you, and I
use hog_threshold(0) to have the clipper app to give back all the time it doesn't
use.

But, on OS/2 I have the possibility to give back the rest of my cpu time slice,
while in linux it usleep()s a fixed amount of time and this makes the program
sluggish without my changes.

regards.



Stas Sergeev ha scritto:

> Hello.
>
> Maximiliano Curia wrote:
> > Yes, that dosemu doesn't detect the clipper idle calls.
> OK, some nice guy at SF finally
> provided a clipper-based program
> for testing (that's why I like
> the SF tracker) and I was able to
> have a look at what it does myself.
> Indeed it calls int21h/1Ch, although
> so infrequently, that it doesn't
> seem to be usefull here.
> It calls int16h/11h a bit more
> frequently, although also rather
> rarely.
> The attached patch makes it to
> release the CPU a little, although
> perhaps still not enough.
> Also note that clipper will work
> in protected mode only in dosemu
> 1.3.1. On any other versions it
> can work in real mode only, which
> may have a different CPU loads.
>
>   ------------------------------------------------------------------------------
> --- src/base/bios/int16.c       Sat Mar 13 00:40:05 2004
> +++ src/base/bios/int16.c       Sat Mar 13 01:15:29 2004
> @@ -126,7 +126,7 @@
>        trigger1=0;
>      if(trigger1 >= config.hogthreshold*500) {
>        if(oldESP==_ESP) {
> -        if (++trigger >= config.hogthreshold*20) {
> +        if (trigger++ >= (config.hogthreshold - 1) * 20) {
>            usleep(INT2F_IDLE_USECS);
>            trigger=0;
>            keyptr = get_key(extended);
>
>   ------------------------------------------------------------------------------
> Scanned by evaluation version of Dr.Web antivirus Daemon
> http://drweb.ru/unix/

--
 __________
|  |  | |__| md2520@mclink.it
|_|_|_|____| Team OS/2 Italia



  reply	other threads:[~2004-03-15 11:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 22:33 Dosemu and clipper applications eating all CPU Stas Sergeev
2004-03-15 11:53 ` Maurilio Longo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-28 17:32 Stas Sergeev
2004-04-28  5:55 Mgr. Peter Tuharsky
2004-04-28 19:52 ` Maximiliano Curia
2004-03-15 19:17 Stas Sergeev
2004-03-15 17:50 Stas Sergeev
2004-03-15 18:07 ` Maurilio Longo
2004-03-11 18:44 Stas Sergeev
2004-03-10 19:36 Stas Sergeev
2004-03-10 22:55 ` Maurilio Longo
2004-03-11  8:29   ` Maurilio Longo
2004-03-10 18:36 Stas Sergeev
2004-03-09 20:16 Stas Sergeev
2004-03-10 15:29 ` Peter B. Steiger
2004-03-10 19:11 ` Maximiliano Curia
2004-03-08 16:11 Maximiliano Curia

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=40559945.CCB3126A@libero.it \
    --to=maurilio.longo@libero.it \
    --cc=linux-msdos@vger.kernel.org \
    /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