From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Dosemu and clipper applications eating all CPU
Date: Wed, 10 Mar 2004 22:36:47 +0300 [thread overview]
Message-ID: <404F6E4F.6060207@aknet.ru> (raw)
Hello.
Maximiliano Curia wrote:
>> Problem of clipper I presume? If it
>> just runs in a busy loop while idle,
>> dosemu can't really help.
> Yes, that dosemu doesn't detect the clipper idle calls.
But *what kind* of idle calls?
This is the vital info. If you
can't find the answer, then the
problem can't be fixed:)
int 0x28 is the real idle call,
but since dosemu catches that,
I suspect clipper does something
else.
> It still eats the cpu, with nice -n 19, but now the 60% is marked as
> nice.
Yes, and the system must not be
crawled now at least. At least in
a theory:)
> I'm trying to understand the freedos idle.
That might be not the case either.
FreeDOS can just call int16 to do
a blocking wait for a keypress, and
that will do the trick.
You have to find out what exactly
the clipper does however.
next reply other threads:[~2004-03-10 19:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 19:36 Stas Sergeev [this message]
2004-03-10 22:55 ` Dosemu and clipper applications eating all CPU Maurilio Longo
2004-03-11 8:29 ` Maurilio Longo
-- 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-12 22:33 Stas Sergeev
2004-03-15 11:53 ` Maurilio Longo
2004-03-11 18:44 Stas Sergeev
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=404F6E4F.6060207@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