From: David Mosberger <davidm@napali.hpl.hp.com>
To: Mario Smarduch <cms063@email.mot.com>
Cc: linux-ia64@linuxia64.org, linux-kernel@vger.kernel.org
Date: Mon, 11 Nov 2002 11:22:59 -0800 [thread overview]
Message-ID: <15824.915.758329.73126@napali.hpl.hp.com> (raw)
In-Reply-To: <3DCFDAE9.6D359448@email.mot.com>
>>>>> On Mon, 11 Nov 2002 10:29:29 -0600, Mario Smarduch <cms063@email.mot.com> said:
Mario> I know that on some commercial Unix systems there are ways to
Mario> cap the CPU utilization by user/group ids are there such
Mario> features/patches available on Linux?
There are probably other patches floating around, but Process Resource
Management (PRM) for Linux is/was one approach to do just that:
http://resourcemanagement.unixsolutions.hp.com/WaRM/prm_linux/
The kernel patches available from this URL are pretty old (up to
2.4.6, as far as I could see), and I'm not sure what the future plans
for PRM on Linux are. Perhaps someone else can provide more details.
--david
next prev parent reply other threads:[~2002-11-11 19:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FAD1088D4556046AEC48D80B47B478C0101F4E7@usslc-exch-4.slc.unisys.com>
2002-11-08 3:51 ` [Linux-ia64] reader-writer livelock problem William Lee Irwin III
2002-11-08 17:13 ` Jeremy Fitzhardinge
2002-11-08 17:25 ` Linus Torvalds
2002-11-08 17:28 ` Linus Torvalds
2002-11-08 17:38 ` Jeremy Fitzhardinge
2002-11-08 17:43 ` David Howells
2002-11-08 17:57 ` Linus Torvalds
2002-11-09 2:48 ` Rusty Russell
2002-11-09 4:36 ` William Lee Irwin III
[not found] ` <3DCFDAE9.6D359448@email.mot.com>
2002-11-11 19:22 ` David Mosberger [this message]
2002-11-12 1:39 ` your mail Rik van Riel
2002-11-08 17:34 ` [Linux-ia64] reader-writer livelock problem David Howells
2002-11-08 17:54 ` David Howells
2002-11-08 17:55 ` Stephen Hemminger
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=15824.915.758329.73126@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=cms063@email.mot.com \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®