From: Robert Love <rml@tech9.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 11:52:19 -0700 [thread overview]
Message-ID: <1027018340.1086.134.camel@sinai> (raw)
In-Reply-To: <1027022323.8154.38.camel@irongate.swansea.linux.org.uk>
On Thu, 2002-07-18 at 12:58, Alan Cox wrote:
> Adjusting the percentages to have a root only zone is doable. It helps
> in some conceivable cases but not all. Do people think its important, if
> so I'll add it
Changing the rules would be easy, but you would need to make the
accounting check for root vs non-root and keep track accordingly.
Admittedly not hard but not entirely pretty either.
I still contend the issues are not related. It would make more sense to
me to do resource limits to solve this problem - rlimits are something
Rik has on his TODO and supposedly easy to add to rmap.
That way people can use strict overcommit, rlimits, neither, or both to
meet their needs.
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/
next prev parent reply other threads:[~2002-07-18 18:52 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 [this message]
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
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=1027018340.1086.134.camel@sinai \
--to=rml@tech9.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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