mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shailabh Nagar" <nagar@us.ibm.com>
To: "Eduardo Cortés" <the_beast@softhome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: limit cpu
Date: Thu, 16 Aug 2001 16:46:06 -0400	[thread overview]
Message-ID: <OF83B3DC6D.E0F03776-ON85256AAA.0070C275@pok.ibm.com> (raw)




Restricting CPU usage alone can be done relatively easily during
recalculate . Before renewing the counter for a task, a quick check could
be made against a newly added user-specific limit. If very precise
accounting is not needed, the check could be done by one of the periodic
daemons.....

But a bigger question remains : will doing this achieve the objective of
isolating a malicious/errant process ? There are a number of other system
resources that the process/user could overuse to the detriment of other
users/processes.

Shailabh


Eduardo Cortés <the_beast@softhome.net>@vger.kernel.org on 08/16/2001
03:22:55 PM

Sent by:  linux-kernel-owner@vger.kernel.org


To:   linux-kernel@vger.kernel.org
cc:
Subject:  Re: Re: limit cpu



On Thursday 16 August 2001 20:54, you wrote:
> > If somebody want to develope it, a lot of thanks. I see scheduler could
> > be better with this feature, opinions?
>
> one excellent reason noone has bothered with it is that hardware
> is dirt cheap.  it's extremely unusual these days to find a machine
> where hostile users are given shell accounts.  for non-hostile
> situations (my lab, for instance), or for servers, the feature is
> useless.
at server level, this feature will be used for virtual hosts (a lot of
ISP's). Could be used at home for security reason limitting any user
95-97%,
and box will be more secure. A lot of people use applications (for XFree)
that could crash the box for this reason.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/




             reply	other threads:[~2001-08-16 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16 20:46 Shailabh Nagar [this message]
     [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 16:08 Eduardo Cortés 
2001-08-16 16:13 ` Mark Hahn
2001-08-16 16:29   ` Eduardo Cortés 
2001-08-16 17:53     ` Hua Zhong
2001-08-16 18:28       ` Eduardo Cortés 
2001-08-17 17:34     ` Rik van Riel

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=OF83B3DC6D.E0F03776-ON85256AAA.0070C275@pok.ibm.com \
    --to=nagar@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=the_beast@softhome.net \
    /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®