All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ram Gupta <ram.gupta5@gmail.com>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: RSS Limit implementation issue
Date: Thu, 09 Feb 2006 23:07:26 +0000	[thread overview]
Message-ID: <1139526447.6692.7.camel@localhost.localdomain> (raw)
In-Reply-To: <728201270602091310r67a3f2dcq4788199f26a69528@mail.gmail.com>

On Iau, 2006-02-09 at 15:10 -0600, Ram Gupta wrote:
> I am working to implement enforcing RSS limits of a process. I am
> planning to make a check for rss limit when setting up pte. If the
> limit is crossed I see couple of  different ways of handling .
> 
> 1. Kill the process . In this case there is no swapping problem.

Not good as the process isn't responsible for the RSS size so it would
be rather random.

> 2. Dont kill the process but dont allocate the memory & do yield as we
> do for init process. Modify the scheduler not to chose the process
> which has already allocated rss upto its limit. When rss usage
> fallsbelow its limit then the scheduler may chose it again to run.
> Here there is a scenario when no page of the process has been freed or
> swapped out because there were enough free pages? Then we need a way
> to reschedule the process by forcefully freeing some pages or need to
> kill the process.

That is what I would expect. Or perhaps even allowing the process to
exceed the RSS but using the RSS limit as a swapper target so that the
process is victimised early. No point forcing swapping and the RSS limit
when there is free memory, only where the resource is contended ..


  reply	other threads:[~2006-02-10 13:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 21:10 RSS Limit implementation issue Ram Gupta
2006-02-09 23:07 ` Alan Cox [this message]
2006-02-10 14:50   ` Ram Gupta
2006-02-10 16:31     ` Kyle Moffett
2006-02-10 22:20     ` Rik van Riel
2006-03-23 16:55   ` Ram Gupta
2006-03-29 20:16     ` Bill Davidsen
2006-03-30 21:41       ` Roger Heflin
2006-04-04 19:28         ` Bill Davidsen
2006-04-05 18:50           ` Roger Heflin
2006-04-07  2:55           ` kingsley
2006-03-31  3:00       ` Peter Chubb
2006-03-31  3:31         ` Bill Davidsen
2006-02-09 23:12 ` Bernd Eckenfels
2006-02-10 21:41 ` Bill Davidsen
     [not found] <mail.linux.kernel/728201270602091310r67a3f2dcq4788199f26a69528@mail.gmail.com>
     [not found] ` <06Feb11.024837est.33911@gpu.utcc.utoronto.ca>
2006-02-13 14:52   ` Ram Gupta
     [not found]     ` <06Feb13.151216est.821021@ugw.utcc.utoronto.ca>
2006-02-13 20:37       ` Ram Gupta
     [not found] <5ErmY-5vN-5@gated-at.bofh.it>
     [not found] ` <5EGm2-2eZ-27@gated-at.bofh.it>
     [not found]   ` <5TBku-7fu-3@gated-at.bofh.it>
2006-03-24 23:06     ` Bodo Eggert

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=1139526447.6692.7.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 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.