linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Szakacsits Szabolcs <szaka@sienet.hu>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] strict VM overcommit for stock 2.4
Date: 18 Jul 2002 15:30:22 -0700	[thread overview]
Message-ID: <1027031422.1555.161.camel@sinai> (raw)
In-Reply-To: <Pine.LNX.4.44L.0207181923180.12241-100000@imladris.surriel.com>

On Thu, 2002-07-18 at 15:24, Rik van Riel wrote:

> I see no reason to not merge this (useful) part. Not only
> is it useful on its own, it's also a necessary ingredient
> of whatever "complete solution" to control per-user resource
> limits.

I am glad we agree here - resource limits and strict overcommit are two
separate solutions to various problems.  Some they solve individually,
others they solve together.

I may use one, the other, both, or neither.  A clean abstract solution
allows this.

	Robert Love

--
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-mm.org/

      reply	other threads:[~2002-07-18 22:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11 22:28 [PATCH] strict VM overcommit Robert Love
2002-07-12 17:30 ` [PATCH] strict VM overcommit for stock 2.4 Robert Love
2002-07-18 15:22   ` Szakacsits Szabolcs
2002-07-18 16:31     ` Robert Love
2002-07-18 16:36       ` Szakacsits Szabolcs
2002-07-18 17:42         ` Robert Love
2002-07-18 17:25           ` Szakacsits Szabolcs
2002-07-18 17:31             ` Szakacsits Szabolcs
2002-07-18 18:32               ` Robert Love
2002-07-18 19:58               ` Alan Cox
2002-07-18 18:01                 ` Szakacsits Szabolcs
2002-07-18 18:52                 ` Robert Love
2002-07-18 20:52                   ` Alan Cox
2002-07-19  6:17                 ` Szakacsits Szabolcs
2002-07-18 22:22               ` Rik van Riel
2002-07-19  7:47                 ` Szakacsits Szabolcs
2002-07-18 18:28             ` Robert Love
2002-07-18 17:50               ` Szakacsits Szabolcs
2002-07-18 19:25                 ` stoffel
2002-07-19  5:52                   ` Szakacsits Szabolcs
2002-07-18 18:56               ` Richard B. Johnson
2002-07-18 19:03                 ` Robert Love
2002-07-18 19:19                   ` Richard B. Johnson
2002-07-18 19:22                     ` Robert Love
2002-07-18 20:49                       ` Alan Cox
2002-07-19 16:49                   ` Amit Shah
2002-07-19 17:16                     ` Robert Love
2002-07-20  5:02                       ` Amit Shah
2002-07-18 19:10                 ` Robert Love
2002-07-18 19:35                   ` Richard B. Johnson
2002-07-18 19:41                     ` Daniel Gryniewicz
2002-07-18 20:23                       ` Richard B. Johnson
2002-07-18 20:43                         ` Daniel Gryniewicz
2002-07-19  7:30                   ` Szakacsits Szabolcs
2002-07-19 18:06                     ` Robert Love
2002-07-18 22:24             ` Rik van Riel
2002-07-18 22:30               ` Robert Love [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=1027031422.1555.161.camel@sinai \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    --cc=szaka@sienet.hu \
    /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