From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ram Gupta <ram.gupta5@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setrlimit for RLIMIT_RSS not enforced
Date: Mon, 09 Jan 2006 14:25:47 +0000 [thread overview]
Message-ID: <1136816747.6659.14.camel@localhost.localdomain> (raw)
In-Reply-To: <728201270601041329r64ee9fb5h3ff015533c762924@mail.gmail.com>
On Mer, 2006-01-04 at 15:29 -0600, Ram Gupta wrote:
> I am wondering why setrlimit for RLIMIT_RSS is not enforced? Is
> there any particular reason for not implementing it? Is there any
> taker if I implement it & submit patch for it?
I had a long long dig back through my mail archive in search of
RLIMIT_RSS. The original mm for Linux didn't enforce it as it did not
have any way to track RSS that was not computationally expensive. The
current mm is probably capable of implementing RSS limits although
questions then still remain about what effect this has if a user sets a
low RSS limit and then causes a lot of swap thrashing.
If you can see a way to implement it efficiently then go for it.
Alan
prev parent reply other threads:[~2006-01-09 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 21:29 setrlimit for RLIMIT_RSS not enforced Ram Gupta
2006-01-09 14:25 ` Alan Cox [this message]
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=1136816747.6659.14.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ram.gupta5@gmail.com \
/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