public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudia Neumann <dr.claudia.neumann@gmx.de>
To: linux-msdos@vger.kernel.org
Subject: Re: Status Update : Deployment of DOSEMU Application Server
Date: Sun, 2 Nov 2008 23:40:01 +0100	[thread overview]
Message-ID: <200811022340.01726.dr.claudia.neumann@gmx.de> (raw)
In-Reply-To: <200810301814.04401.manfred.scherer.mhm@t-online.de>

Hi Manfred!

I tried your patches, but they didn't work out as they should on 1.3.4 and 
1.4.0. 

I had the same problem with some other program on Linux kernel 2.6.24. They 
changed kernel idle time handling somewhere between 2.6.18 and 2.6.24. Now in 
some programs, and dosemu is one of them, the CPU load runs high to over 90% 
on current Linux kernels. 

Perhaps someone knows where to change that in the source code.

Regards

Claudia

Am Donnerstag Oktober 30 2008 18:14 schrieben Sie:
> For the 100% CPU-load problem caused by clipper programs and other dos
> programs, I use two small patches in dosemu 1.3.4:
>
> --- ./base/bios/int16.c.ORIG    2006-10-31 21:28:54.000000000 +0100
> +++ ./base/bios/int16.c 2006-12-31 13:37:10.000000000 +0100
> @@ -118,7 +118,11 @@
>        trigger_idle();
>      else
>        reset_idle(0);
> -    idle(500, 20, 0, INT2F_IDLE_USECS, "int16");
> +    /* 2006-12-13
> +     * dbase3+, word4.0, .... CPU-load is to heavy during idle. --ms
> +     * idle(500, 20, 0, INT2F_IDLE_USECS, "int16");
> +     */
> +    idle(10, 20, 0, INT2F_IDLE_USECS, "int16");
>    } else {
>      reset_idle(1);
>    }
>
> --- ./base/async/int.c.ORIG     2006-11-12 02:20:26.000000000 +0100
> +++ ./base/async/int.c  2007-01-22 15:12:30.000000000 +0100
> @@ -1232,7 +1232,13 @@
>  #endif
>
>    case 0x2C: {                   /* get time & date */
> -      idle(2, 100, 0, INT2F_IDLE_USECS, "dos_time");
> +      /*
> +       * 2004/08/20, 2006/11/25
> +       * waiting loops, like 'wait until time ...' call never a
> trigger_idle() +       * but 90% cpu load. --ms
> +       * idle(2, 100, 0, INT2F_IDLE_USECS, "dos_time");
> +       */
> +      idle(0, 20, 0, INT2F_IDLE_USECS, "dos_time");
>        return 0;
>      }
>
> maybe this can solve your 100% CPU-load too.
>
> Manfred
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2008-11-02 22:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 17:14 Status Update : Deployment of DOSEMU Application Server Manfred Scherer
2008-11-02 22:40 ` Claudia Neumann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-08 16:49 Manfred Scherer
2008-11-09  8:24 ` Claudia Neumann
2008-10-30  9:02 Shaw Tong Tan
2008-10-30 13:42 ` Ivan Baldo
2008-10-30 13:43 ` Alain M.
2008-10-30 13:45 ` Alain M.
2008-10-29  5:43 Shaw Tong Tan
2008-10-29 14:33 ` Alain M.
2008-10-29 18:36   ` Andrew Joakimsen
2008-10-29 21:15     ` Alain M.
2008-10-29 21:47       ` Andrew Joakimsen
2008-10-30  1:57   ` Shaw Tong Tan
2008-10-31  0:10     ` Andrew Joakimsen
2008-10-31  2:59       ` Shaw Tong Tan

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=200811022340.01726.dr.claudia.neumann@gmx.de \
    --to=dr.claudia.neumann@gmx.de \
    --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