From: James Cleverdon <jamesclv@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org,
Rik van Riel <riel@conectiva.com.br>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Kswapd madness in 2.4 kernels
Date: Tue, 5 Nov 2002 14:13:00 -0800 [thread overview]
Message-ID: <200211051413.00661.jamesclv@us.ibm.com> (raw)
In-Reply-To: <3DB8C941.DEF1C069@digeo.com>
Status report:
Due to dependencies, I didn't try the two recommended patches alone. I ran
Andrea's 2.4.20-pre10aa1 kernel on the test load for one week. Low memory
was conserved and kswapd never went out of control. Presumably,
05_vm_16_active_free_zone_bhs-1 did the job for buffers, and the inode patch
continued to work.
Are there any plans on getting these into 2.4.21?
On Thursday 24 October 2002 09:32 pm, Andrew Morton wrote:
> James Cleverdon wrote:
> > Andrea_Archangeli-inode_highmem_imbalance.patch Type: text/x-diff
>
> That's in -aa kernels, is correct and is needed.
>
> > Andrew_Morton-2.4_VM_sucks._Again.patch Type: text/x-diff
>
> hmm. Someone seems to have renamed my nuke-buffers patch ;)
>
> My main concern is that this was a real quickie; it does a very
> aggressive takedown of buffer_heads. Andrea's kernels contain a
> patch which takes a very different approach. See
> http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.20pre
>8aa2/05_vm_16_active_free_zone_bhs-1
>
> I don't think anyone has tried that patch in isolation though...
>
> If nuke-buffers passes testing and doesn't impact performance then
> fine. A more cautious approach would be to use the active_free_zone_bhs
> patch. If that proves inadequate then add in the "read" part of
> nuke-buffers. That means dropping the fs/buffer.c part.
> -
On Friday 25 October 2002 09:57 am, Rik van Riel wrote:
> On Thu, 24 Oct 2002, James Cleverdon wrote:
> > We have some customers with some fairly beefy servers. They can get the
> > system into an unusable state that has been reported on lkml before.
> >
> > The two attached patches applied to 2.4.19 fix the problem on our test
> > boxes.
> >
> > Are these patches still considered a good idea for 2.4? Is there
> > something better I should be using?
>
> Yes, these patches are a good idea. I'm curious why they
> haven't been submitted to Marcelo yet ;)
>
> Rik
--
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com
next prev parent reply other threads:[~2002-11-05 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 3:26 James Cleverdon
2002-10-25 4:32 ` Andrew Morton
2002-11-05 22:13 ` James Cleverdon [this message]
2002-11-06 11:11 ` Andrea Arcangeli
2002-11-06 13:18 ` Marcelo Tosatti
2002-11-06 16:40 ` Andrea Arcangeli
2002-10-25 16:57 ` Rik van Riel
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=200211051413.00661.jamesclv@us.ibm.com \
--to=jamesclv@us.ibm.com \
--cc=akpm@digeo.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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