linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Eric W. Biederman" <ebiederman@uswest.net>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Mark_H_Johnson.RTS@raytheon.com, linux-mm@kvack.org,
	riel@nl.linux.org
Subject: Re: pressuring dirty pages (2.3.99-pre6)
Date: Wed, 26 Apr 2000 12:06:38 +0100	[thread overview]
Message-ID: <20000426120638.F3792@redhat.com> (raw)
In-Reply-To: <m1snwadmcp.fsf@flinx.biederman.org>; from ebiederman@uswest.net on Tue, Apr 25, 2000 at 02:14:30PM -0500

Hi,

On Tue, Apr 25, 2000 at 02:14:30PM -0500, Eric W. Biederman wrote:

> Right.  A RSS guarantee sounds like it would make for easier tuning.
> But a hard RSS max has the advantage of hitting a memory space hog
> early, before it has a chance to get all of memory dirty, and simply
> penalizes the hog.  

Agreed --- RSS limits for the biggest processes in the system are
definitely needed.
 
> Also under heave load a RSS garantee and a RSS hard limit are the
> same.

Not at all --- that's only the case if you only have one process 
experiencing memory pressure, or if you are in equilibrium.  It's the
bits in between, where we are under changing load, which are the most
interesting, and in that case you still want your smallest processes to
have the protection of the RSS guarantees while you start dynamically
reducing the RSS limit on the biggest processes.

--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  parent reply	other threads:[~2000-04-26 11:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-25 14:27 Mark_H_Johnson.RTS
2000-04-25 16:30 ` Stephen C. Tweedie
2000-04-25 19:14   ` Eric W. Biederman
2000-04-25 19:47     ` Rik van Riel
2000-04-26 11:43       ` Stephen C. Tweedie
2000-04-26 11:06     ` Stephen C. Tweedie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-24 19:54 Rik van Riel
2000-04-24 21:27 ` Stephen C. Tweedie
2000-04-24 22:42   ` Rik van Riel
2000-04-25  9:35     ` Stephen C. Tweedie
2000-04-25 15:25       ` Rik van Riel
2000-04-25 13:58     ` Eric W. Biederman

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=20000426120638.F3792@redhat.com \
    --to=sct@redhat.com \
    --cc=Mark_H_Johnson.RTS@raytheon.com \
    --cc=ebiederman@uswest.net \
    --cc=linux-mm@kvack.org \
    --cc=riel@nl.linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox