public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RSS ulimit enforcement for 2.6.8
Date: Fri, 06 Aug 2004 12:22:15 +1000	[thread overview]
Message-ID: <4112EB57.2020003@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0408052056160.8229-100000@dhcp83-102.boston.redhat.com>

Rik van Riel wrote:

>On Thu, 5 Aug 2004, Andrew Morton wrote:
>
>
>>Good question.  What I'm groping for here is some definition of what we
>>actually want the feature to _do_.  Once we have that, and have suitably
>>argued about it, we can then go off and see if the patch actually does it.
>>
>
>What I want the feature to do is allow users to set an
>RSS rlimit to prevent a process from hogging up all the
>machine's memory.
>
>I am not looking for a hard memory limit, since that
>would just cause extra IO, which has bad consequences
>for the rest of the system.
>
>In addition, I would like the patch to be relatively
>low impact, not giving us much maintenance overhead or
>much runtime overhead.
>
>If anybody has good reasons for needing hard per-process
>RSS limits, let us know.  So far I haven't seen anybody
>with a workload that somehow requires a hard limit.
>
>
FWIW, I like Rik's approach. One tiny request might be just to do the
patch underneath the thrashing control patch so it can be sent to Linus
earlier.


      reply	other threads:[~2004-08-06  2:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 17:05 [PATCH] RSS ulimit enforcement for 2.6.8 Rik van Riel
2004-08-05 20:34 ` Bill Davidsen
2004-08-05 20:49   ` Rik van Riel
2004-08-05 21:20     ` Andrew Morton
2004-08-10  7:28       ` Kurt Garloff
2004-08-08  3:09     ` Bill Davidsen
2004-08-05 22:31 ` Andrew Morton
2004-08-06  0:19   ` Rik van Riel
2004-08-06  0:36     ` Andrew Morton
2004-08-06  0:51       ` Rik van Riel
2004-08-06  0:53         ` Andrew Morton
2004-08-06  0:59           ` Rik van Riel
2004-08-06  2:22             ` Nick Piggin [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=4112EB57.2020003@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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