public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: DOSEmu on SMP systems.
Date: Tue, 26 Aug 2003 21:08:47 +0400	[thread overview]
Message-ID: <3F4B941F.2060208@aknet.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

Hello.

Sergey Suleymanov wrote:
> I have Tyan Athlon MP platform with Linux kernel 2.4.21. Dosemu 
> eats ~30 %CPU time in a plain DOS command prompt. Playing with 
> config.hogthreshold multipliers in int.c, int16.c and *_IDLE_USECS
> values gives nothing.
Not sure about an SMP, but the $_hogthreshold
doesn't work reliably for me without the
attached patch. See if probably it helps you.

[-- Attachment #2: int16.diff --]
[-- Type: text/plain, Size: 854 bytes --]

--- int16.c.old	Mon Jun 23 04:02:08 2003
+++ int16.c	Tue Aug 26 21:02:31 2003
@@ -116,7 +116,6 @@
 static unsigned check_key_available(int extended)
 {
   unsigned keyptr = get_key(extended);
-  static Bit32u oldESP;
   static int trigger = 0, trigger1 = 0;
   
   if(keyptr == -1 && config.hogthreshold && CAN_SLEEP()) {
@@ -125,17 +124,12 @@
     else
       trigger1=0;
     if(trigger1 >= config.hogthreshold*500) {
-      if(oldESP==_ESP) {
-        if (++trigger >= config.hogthreshold*20) {
-          usleep(INT2F_IDLE_USECS);
-          trigger=0;
-          keyptr = get_key(extended);
-        }
-      } else {
+      if (++trigger >= config.hogthreshold*20) {
+        usleep(INT2F_IDLE_USECS);
         trigger=0;
+        keyptr = get_key(extended);
       }
       trigger1--;
-      oldESP=_ESP;
     }
   }
   return get_key(extended);

             reply	other threads:[~2003-08-26 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 17:08 Stas Sergeev [this message]
2003-08-28  5:31 ` DOSEmu on SMP systems Sergey Suleymanov
2003-08-28 12:24   ` Sergey Suleymanov
  -- strict thread matches above, loose matches on Subject: below --
2003-08-26  7:57 Sergey Suleymanov

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=3F4B941F.2060208@aknet.ru \
    --to=stsp@aknet.ru \
    --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