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: <200706212100.28381.jjj@gmx.de>
Date:	Thu, 21 Jun 2007 21:00:28 +0200
From:	Jan Kandziora <jjj@....de>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Limiting load of certain processes

Am Donnerstag, 21. Juni 2007 20:26 schrieb Jan Engelhardt:
>
> 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.
>
Well, the "tamedos" shareware does it that way. It works fairly well, but not 
too well. DOSEMU doesn't address this problem besides from the suspending 
whenever the dosemu window is iconified.

My idea was *not* to schedule a process for running, even if it is the only 
runnable one, if it is marked as a "presumably bad mannered" process and 
consumed its previous timeslice to the whole. Instead an idle slice is done. 
After a configureable amount of time, the bad mannered process is allowed to 
run again.

I know it's a crude idea for everyday Linux processes, but for dosemu driven 
applications, which behave badly in a multitasking OS *and* for which source 
code isn't available, it may be worth to discuss.

Kind regards

	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/