From: Daniel Phillips <phillips@bonn-fries.net>
To: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>,
linux-kernel@vger.kernel.org
Subject: Re: Google's mm problems
Date: Sun, 4 Nov 2001 04:29:39 +0100 [thread overview]
Message-ID: <20011104032828Z16097-4784+757@humbolt.nl.linux.org> (raw)
In-Reply-To: <E15yhyY-0000Yb-00@starship.berlin> <20011103205601.2170.qmail@thales.mathematik.uni-ulm.de>
In-Reply-To: <20011103205601.2170.qmail@thales.mathematik.uni-ulm.de>
On November 3, 2001 09:56 pm, Christian Ehrhardt wrote:
> On Wed, Oct 31, 2001 at 12:07:17AM +0100, Daniel Phillips wrote:
> > Hi, I've been taking a look on a mm problem that Ben Smith of Google posted
> > a couple of weeks ago. As it stands, Google can't use 2.4 yet because all
> > known flavors of 2.4 mm fall down in one way or another. This is not good.
>
> Andrea suggested that this might be a mlock bug and someone else
> pointed out that madvise instead of mlock exhibits similar behaviour.
> So I looked at this code and this patch looks obviously correct:
I'm pretty sure at this point that it's just poor balancing between zones. To
test this, Ben tried it highmem config'ed off and ran without problems (2/2G
user/kernel split).
--
Daniel
next prev parent reply other threads:[~2001-11-04 3:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 23:07 Daniel Phillips
2001-11-01 20:00 ` Google's mm problems with 2.4.13 and 4G of memory Sven Heinicke
2001-11-02 22:24 ` Daniel Phillips
2001-11-03 20:56 ` Google's mm problems Christian Ehrhardt
2001-11-04 3:29 ` Daniel Phillips [this message]
2001-11-05 16:10 ` Sven Heinicke
2001-11-09 9:38 ` 2.4.>=13 VM/kswapd/shmem/Oracle issue (was Re: Google's mm problems) Ken Brownfield
2001-11-09 22:39 ` vda
2001-11-15 17:40 ` Andrea Arcangeli
2001-11-15 17:48 ` Arjan van de Ven
2001-11-17 15:54 ` Andrea Arcangeli
2001-11-18 6:17 ` Mike Galbraith
2001-11-18 6:27 ` Andrea Arcangeli
2001-11-18 7:14 ` Mike Galbraith
2001-11-15 20:07 ` Ken Brownfield
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=20011104032828Z16097-4784+757@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=ehrhardt@mathematik.uni-ulm.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®