From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stas Sergeev Subject: Re: Dosemu and clipper applications eating all CPU Date: Tue, 09 Mar 2004 23:16:52 +0300 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <404E2634.8080109@aknet.ru> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-msdos@vger.kernel.org Hello. Maximiliano Curia wrote: > I'm trying to run a clipper program inside dosemu. It runs ok, but it > eats all the CPU cycles when it's idle. You haven't specified your dosemu version. > I've already tried changing the hogthreshold value, with no changes in > the result. You must keep that value to 1 - that's the most optimistic one. > I've been told this is a known problem, Problem of clipper I presume? If it just runs in a busy loop while idle, dosemu can't really help. > but I'm hoping it can be fixed > in some way. You can assign a lower priority level to dosemu process, see nice/renice commands. That will help as to not crawling the system any more. You can also try the patches from here: https://sourceforge.net/tracker/index.php?func=detail&aid=716137&group_id=49784&atid=457450 They release the CPU cycles by making dosemu slower, which is perhaps also not what you really want. The real solution (if it exists) can be found if you trace your program with dosdebug, see what it really does when idle, and think about adding the appropriate heuristic to dosemu to catch that case (but it already catches most of the common "idling" cases).