From: Robert Love <rml@tech9.net>
To: root@chaos.analogic.com
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 12:03:16 -0700 [thread overview]
Message-ID: <1027018996.1116.136.camel@sinai> (raw)
In-Reply-To: <Pine.LNX.3.95.1020718144203.1123A-100000@chaos.analogic.com>
On Thu, 2002-07-18 at 11:56, Richard B. Johnson wrote:
> What should have happened is each of the tasks need only about
> 4k until they actually access something. Since they can't possibly
> access everything at once, we need to fault in pages as needed,
> not all at once. This is what 'overcomit' is, and it is necessary.
Then do not enable strict overcommit, Dick.
> If you have 'fixed' something so that no RAM ever has to be paged
> you have a badly broken system.
That is not the intention of Alan or I's work at all.
Robert Love
next prev parent reply other threads:[~2002-07-18 19:00 UTC|newest]
Thread overview: 53+ 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 [this message]
2002-07-18 19:19 ` Richard B. Johnson
2002-07-18 19:22 ` Robert Love
2002-07-18 20:49 ` Alan Cox
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
2002-07-18 22:08 ` [PATCH] strict VM overcommit Adrian Bunk
2002-07-18 22:27 ` Robert Love
2002-07-19 11:02 ` Adrian Bunk
2002-07-20 0:32 ` Alan Cox
2002-07-21 9:10 ` Szakacsits Szabolcs
2002-07-21 13:32 ` Alan Cox
2002-07-21 12:46 ` Adrian Bunk
2002-07-21 14:33 ` Jos Hulzink
2002-07-22 0:43 ` Thunder from the hill
2002-07-21 16:46 ` Alan Cox
2002-07-21 15:23 ` Szakacsits Szabolcs
2002-07-21 19:01 ` Alan Cox
2002-07-22 8:08 ` Szakacsits Szabolcs
2002-07-22 13:00 ` Alan Cox
2002-07-22 12:45 ` Hugh Dickins
2002-07-22 14:01 ` Alan Cox
2002-07-22 1:12 ` Thunder from the hill
2002-07-22 8:03 ` Szakacsits Szabolcs
2002-07-22 10:23 ` Thunder from the hill
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=1027018996.1116.136.camel@sinai \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=root@chaos.analogic.com \
--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
Powered by JetHome