From: Frederik Dannemare <tux@sentinel.dk>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Limiting max cpu usage per user (old Conectiva patch)
Date: Wed, 27 Nov 2002 16:19:21 +0100 [thread overview]
Message-ID: <3DE4E279.6010406@sentinel.dk> (raw)
In-Reply-To: Pine.LNX.4.44L.0211271008370.4103-100000@imladris.surriel.com
Rik van Riel wrote:
> On Wed, 27 Nov 2002, Frederik Dannemare wrote:
>
>>do we have an effective way to limit max cpu usage per user? I haven't been
>>able to find much useful info except for an old thread on lkml, where Rik
>>van Riel mentions[1] a 2.2 kernel patch by Conectiva.
>>
>>Anybody knows if this patch (or similar functionality) been ported to 2.4
>>(or 2.5)?
>
> It's on my patches page:
>
> http://surriel.com/patches/
>
Great. Many thanks. I'll go test it right away.
--
Frederik
next prev parent reply other threads:[~2002-11-27 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 10:11 Limiting max cpu usage per user (old Conectiva patch) Frederik Dannemare
2002-11-27 12:08 ` Rik van Riel
2002-11-27 13:52 ` hugang
2002-11-27 15:19 ` Frederik Dannemare [this message]
2002-11-27 20:09 ` Martin Waitz
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 23:11 Marc-Christian Petersen
2002-11-28 12:34 ` Frederik Dannemare
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=3DE4E279.6010406@sentinel.dk \
--to=tux@sentinel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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