linux-kernel - Re: Limiting CPU usage for processes in linux 2.6.18.8

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] [day] [month] [year] [list]

Date:	Mon, 31 Mar 2008 11:25:32 -0400
From:	"Bryan Donlan" <bdonlan@...il.com>
To:	"Eric Descourtis" <desc0068@...onquincollege.com>
Cc:	linux-kernel@...r.kernel.org, eric.des.courtis@...il.com
Subject: Re: Limiting CPU usage for processes in linux 2.6.18.8

On Sun, Mar 30, 2008 at 9:37 PM, Eric Descourtis
<desc0068@...onquincollege.com> wrote:
> Hello,
>
>  I would like to implement a patch to the scheduler that limits the CPU usage of individual
>  processes to a percentage in Linux 2.6.18.8 (Can't be any other version).
>  I would just like some feedback on the following questions:
>
>  1. How can I ensure that limited processes get their CPU time percentage allocation?
>  2. Are there mechanisms in place that would simplify this process?
>
>  I have been hitting my head against the wall for a long time now, any help would be appreciated.

The scheduler isn't really designed to force programs to idle when
there's nothing else to run - that would be a waste :)

If the reason you're on 2.6.18.8 is for Xen, you might want to try
using a recent kernel with paravirt ops, and use the CFS fair group
(or user) scheduler to set cpu shares. See
Documentation/sched-design-CFS.txt . If you really want to eat up a
certain portion of CPU time doing nothing, you could create a program
to busy-loop to starve the others and set CPU shares appropriately,
though I don't really see the point in that.
--
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/