linux-kernel - Re: Limiting load of certain processes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0706212020520.26568@fbirervta.pbzchgretzou.qr>
Date:	Thu, 21 Jun 2007 20:26:14 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Jan Kandziora <jjj@....de>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Limiting load of certain processes

On Jun 21 2007 19:50, Jan Kandziora wrote:
>
>Dear all,
>
>I like to use an old DOS/Clipper application through DOSEMU on a Linux
>application server in a hotel. It works, but (as usual with DOS), it causes
>a processor load of 100% in certain situations, while just waiting for user
>interaction.

That's how it is. When DOS was written, cpu relaxing like the HLT instruction
was not known yet (or was it?), so everything was (and still is) a busy loop.

(Yes, including today's typical x86 BIOSes. Aw crap!)

Of course there may be hacks that try to figure out if a DOS window is idle,
waiting for user input. (Seems like a new invention in Windows 2000 and up).
Since dosemu and all the emulators are not running a genuine Microsoft DOS /
have source, it should be easy game for them to wait non-busily. Or maybe
busy-waiting is _part_ of the emulation; maybe some DOS driver(s) require it.

	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/