From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.4 VM sucks. Again
Date: Thu, 23 May 2002 09:46:08 -0700 [thread overview]
Message-ID: <399720000.1022172368@flay> (raw)
In-Reply-To: <200205231629.g4NGTWE22956@mail.pronto.tv>
>> > Starting up 30 downloads from a custom HTTP server (or Tux - or Apache -
>> > doesn't matter), file size is 3-6GB, download speed = ~4.5Mbps. After
>> > some time the kernel (a) goes bOOM (out of memory) if not having any
>> > swap, or (b) goes gong swapping out anything it can.
>>
>> How much RAM do you have, and what does /proc/meminfo
>> and /proc/slabinfo say just before the explosion point?
>
> I have 1 gig - highmem (not enabled) - 900 megs.
> for what I can see, kernel can't reclaim buffers fast enough.
> ut looks better on -aa.
Sounds like exactly the same problem we were having. There are two
approaches to solving this - Andrea has a patch that tries to free them
under memory pressure, akpm has a patch that hacks them down as soon
as you've fininshed with them (posted to lse-tech mailing list). Both approaches
seemed to work for me, but the performance of the fixes still has to be established.
I've seen over 1Gb of buffer_heads ;-)
M.
next prev parent reply other threads:[~2002-05-23 16:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 13:11 [BUG] 2.4 VM sucks. Again Roy Sigurd Karlsbakk
2002-05-23 14:54 ` Martin J. Bligh
2002-05-23 16:29 ` Roy Sigurd Karlsbakk
2002-05-23 16:46 ` Martin J. Bligh [this message]
2002-05-24 10:04 ` Roy Sigurd Karlsbakk
2002-05-24 14:35 ` Martin J. Bligh
2002-05-24 19:32 ` Andrew Morton
2002-05-30 10:29 ` Roy Sigurd Karlsbakk
2002-05-30 19:28 ` Andrew Morton
2002-05-31 16:56 ` Roy Sigurd Karlsbakk
2002-05-31 18:19 ` Andrea Arcangeli
2002-06-18 11:26 ` Roy Sigurd Karlsbakk
2002-06-18 19:42 ` Andrew Morton
2002-06-19 11:26 ` Roy Sigurd Karlsbakk
2002-07-10 7:50 ` [2.4 BUFFERING BUG] (was [BUG] 2.4 VM sucks. Again) Roy Sigurd Karlsbakk
2002-07-10 8:05 ` Andrew Morton
2002-07-10 8:14 ` Roy Sigurd Karlsbakk
2002-08-28 9:28 ` [BUG+FIX] 2.4 buggercache sucks Roy Sigurd Karlsbakk
2002-08-28 15:30 ` Martin J. Bligh
2002-08-29 8:00 ` Roy Sigurd Karlsbakk
2002-08-29 13:42 ` Martin J. Bligh
2002-08-30 9:21 ` Roy Sigurd Karlsbakk
2002-08-30 17:19 ` Martin J. Bligh
2002-08-30 18:49 ` Andrew Morton
2002-05-24 15:11 ` [BUG] 2.4 VM sucks. Again Alan Cox
2002-05-24 15:53 ` Martin J. Bligh
2002-05-24 16:14 ` Alan Cox
2002-05-24 16:31 ` Martin J. Bligh
2002-05-24 17:30 ` Austin Gonyou
2002-05-24 17:43 ` Martin J. Bligh
2002-05-24 18:03 ` Austin Gonyou
2002-05-24 18:10 ` Martin J. Bligh
2002-05-24 18:29 ` 2.4 Kernel Perf discussion [Was Re: [BUG] 2.4 VM sucks. Again] Austin Gonyou
2002-05-24 19:01 ` Stephen Frost
2002-05-27 9:24 ` [BUG] 2.4 VM sucks. Again Marco Colombo
2002-05-27 22:24 ` Austin Gonyou
2002-05-27 23:08 ` Austin Gonyou
2002-05-27 11:12 ` Roy Sigurd Karlsbakk
2002-05-27 14:31 ` Alan Cox
2002-05-27 13:43 ` Roy Sigurd Karlsbakk
2002-05-23 16:03 ` Johannes Erdfelt
2002-05-23 16:33 ` Roy Sigurd Karlsbakk
2002-05-23 22:50 ` Luigi Genoni
2002-05-24 11:53 ` Roy Sigurd Karlsbakk
2002-05-23 18:12 ` jlnance
2002-05-24 10:36 ` Roy Sigurd Karlsbakk
2002-05-31 21:21 ` Andrea Arcangeli
2002-06-01 12:36 ` Roy Sigurd Karlsbakk
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=399720000.1022172368@flay \
--to=martin.bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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