mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven Heinicke <sven@research.nj.nec.com>
To: linux-kernel@vger.kernel.org
Subject: Google's mm problems with 2.4.13 and 4G of memory
Date: Thu, 1 Nov 2001 15:00:42 -0500 (EST)	[thread overview]
Message-ID: <15329.43498.436892.985755@abasin.nj.nec.com> (raw)
In-Reply-To: <E15yhyY-0000Yb-00@starship.berlin>
In-Reply-To: <E15yhyY-0000Yb-00@starship.berlin>


I got a Dell powerEdge something with 4G of memory locking up pritty
hard when Danial Phillips test program hits chunk 9:

mlocking at 401bf000 of size 1048576
mlock took 12.181794 seconds
munlock'ed 5999e000
munmap'ed 5999e000
Loading data at 5999e000 for slot 1
Load (/mnt/sdb/sven/chunk9) succeeded!
mlocking slot 1, 5999e000
mlocking at 5999e000 of size 1048576


And nothing.  It's a vanilla 2.4.13 kernel and Mandrake 8.0.

If I run the program up to like chunk 3 and send an interrupt it
doesn't free up the memory unless I umount the file system.

Please suggest idea on how to fix it.  I have this system to abuse for
several days.

      Sven

  reply	other threads:[~2001-11-01 20:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30 23:07 Google's mm problems Daniel Phillips
2001-11-01 20:00 ` Sven Heinicke [this message]
2001-11-02 22:24   ` Google's mm problems with 2.4.13 and 4G of memory Daniel Phillips
2001-11-03 20:56 ` Google's mm problems Christian Ehrhardt
2001-11-04  3:29   ` Daniel Phillips
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=15329.43498.436892.985755@abasin.nj.nec.com \
    --to=sven@research.nj.nec.com \
    --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®