From: "Eduardo Cortés " <the_beast@softhome.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Re: limit cpu
Date: Thu, 16 Aug 2001 18:29:15 +0200 [thread overview]
Message-ID: <20010816162913Z271588-760+2494@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10108161610150.19342-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10108161610150.19342-100000@coffee.psychology.mcmaster.ca>
On Thursday 16 August 2001 18:13, you wrote:
> > > > i want to know if linux can limit the max cpu usage (not cpu time)
> > > > per user,
> > >
> > > no. doing so would inherently slow down the scheduler.
> >
> > but *BSD has this feature, what's the problem in linux?
>
> I said that, thinking that it would require another test along
> the scheduler's fast path. but if we only test when a process
> has exhausted its quantum (or perhaps at counter-recalc),
> the overhead would be minor.
I think that it's a good feature for linux, but I don't know if is very
complex to develope in linux. If I can limit the max cpu usage (in %) for an
user/group, the box is more solid.
next prev parent reply other threads:[~2001-08-16 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 16:08 Re: limit cpu Eduardo Cortés
2001-08-16 16:13 ` Mark Hahn
2001-08-16 16:29 ` Eduardo Cortés [this message]
2001-08-16 17:53 ` Hua Zhong
2001-08-16 18:28 ` Eduardo Cortés
2001-08-17 17:34 ` Rik van Riel
[not found] <Pine.LNX.4.10.10108161853020.19342-100000@coffee.psychology.mcmaster.ca>
2001-08-16 19:22 ` Eduardo Cortés
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 20:46 Shailabh Nagar
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=20010816162913Z271588-760+2494@vger.kernel.org \
--to=the_beast@softhome.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.