From: William Lee Irwin III <wli@holomorphy.com>
To: "M. Edward Borasky" <znmeb@aracnet.com>
Cc: linux-kernel@vger.kernel.org, Martin.Bligh@us.ibm.com,
andrea@suse.de, riel@surriel.com, torvalds@transmeta.com,
akpm@zip.com.au
Subject: Re: Have the 2.4 kernel memory management problems on large machines been fixed?
Date: Wed, 22 May 2002 07:36:51 -0700 [thread overview]
Message-ID: <20020522143651.GA14918@holomorphy.com> (raw)
In-Reply-To: <20020522085111.C20554@ds217-115-141-141.dedicated.hosteurope.de> <HBEHIIBBKKNOBLMPKCBBGEBEENAA.znmeb@aracnet.com>
On Wed, May 22, 2002 at 07:00:11AM -0700, M. Edward Borasky wrote:
> A few months ago, there was a flurry of reports from people having
> difficulties with memory management on large machines (ia32 over 4 GB). I've
> seen a lot of 2.4.x-yy kernels go by and much VM discussion, but what I'm
> *not* seeing is reports of either catastrophic behavior or its absence on
> large machines. I haven't had a chance to run my own test cases on the
> 2.4.18 kernel from Red Hat 7.3 yet, so I can't make any personal
> contribution to this discussion.
The catastrophic failures are still happening, in fact, the last
lse-tech conference call a week or two ago was dedicated at least in
part to them. The number of different ways in which these failures
occur is large, so it's taking a while for the iterations of whack-a-mole
game to converge to kernel stability. Andrea has probably been doing the
most visible stuff on this front with the recent bh/inode exhaustion
patches, with due credit to akpm as well for the unconditional bh
stripping patch.
Cheers,
Bill
next prev parent reply other threads:[~2002-05-22 14:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 6:51 2.4.19pre*: IO statistics in /proc/partitions corrupt Jochen Suckfuell
2002-05-22 14:00 ` Have the 2.4 kernel memory management problems on large machines been fixed? M. Edward Borasky
2002-05-22 14:08 ` bert hubert
2002-05-22 14:55 ` Alan Cox
2002-05-22 15:56 ` Martin J. Bligh
2002-05-22 16:23 ` Alan Cox
2002-05-22 21:46 ` Doug Ledford
2002-05-22 14:36 ` William Lee Irwin III [this message]
2002-05-22 15:44 ` Martin J. Bligh
2002-05-22 15:53 ` Martin J. Bligh
2002-05-22 16:07 ` William Lee Irwin III
2002-05-22 16:36 ` Martin J. Bligh
2002-05-22 17:21 ` Andrea Arcangeli
2002-05-22 18:18 ` Martin J. Bligh
2002-05-22 18:02 ` Alan Cox
2002-05-22 18:08 ` Linus Torvalds
2002-05-22 18:30 ` Rik van Riel
2002-05-22 18:40 ` Linus Torvalds
2002-05-22 18:48 ` Martin J. Bligh
2002-05-22 18:34 ` Have the 2.4 kernel memory management problems on large machines Alan Cox
2002-05-22 18:27 ` Linus Torvalds
2002-05-22 20:30 ` Have the 2.4 kernel memory management problems on large machines been fixed? William Lee Irwin III
2002-05-22 21:18 ` Martin J. Bligh
2002-05-22 21:23 ` Linus Torvalds
2002-05-22 22:35 ` Andrea Arcangeli
2002-05-22 22:44 ` Martin J. Bligh
2002-05-28 2:08 ` Wim Coekaerts
2002-05-31 20:39 ` Andrea Arcangeli
2002-05-23 14:16 ` Bill Davidsen
2002-05-23 17:18 ` Linus Torvalds
2002-05-23 19:34 ` Bill Davidsen
2002-05-23 19:46 ` Linus Torvalds
2002-05-22 18:38 ` Martin J. Bligh
2002-05-22 17:50 ` Alan Cox
2002-05-22 17:54 ` J Sloan
2002-05-22 18:22 ` Have the 2.4 kernel memory management problems on large machines Alan Cox
2002-05-22 22:14 ` J Sloan
2002-05-22 18:24 ` Have the 2.4 kernel memory management problems on large machines been fixed? Martin J. Bligh
2002-05-22 22:05 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 14:29 Alastair Stevens
[not found] <E17AaR0-0002QM-00@the-village.bc.nu.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0205221048570.23621-100000@penguin.transmeta.com.suse.lists.linux.kernel>
2002-05-22 20:23 ` Andi Kleen
2002-05-22 20:58 ` Linus Torvalds
2002-05-23 12:40 ` Mike Jagdis
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=20020522143651.GA14918@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.com \
--cc=torvalds@transmeta.com \
--cc=znmeb@aracnet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.