From: Dan Aloni <da-x@monatomic.org>
To: Pedram M <pmessri@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: kswapd issues + kernel 2.4.21-32.0.1.ELsmp
Date: Sun, 1 Apr 2007 13:21:28 +0300 [thread overview]
Message-ID: <20070401102127.GA16987@localdomain> (raw)
In-Reply-To: <9c9aa5d00703310111w3809fd56t75bcde9d5047ca81@mail.gmail.com>
On Sat, Mar 31, 2007 at 01:11:29AM -0700, Pedram M wrote:
> Hi,
>
> I've seen this around, and have heard about it in forums and else-where,
> could somebody enlighten me with more information or with experiences
> they have had. Looks like kswapd begins to eat CPU dramatically till the
> box eventually locks up.
My experience with kswapd eating a lot of CPU tells that this particular
problem with Linux 2.4 manifests itself on this scenario:
* No swap is configured (we are blessed with RAM).
_AND_:
* A lot of memory is allocated (for my case: a lot of anonymous pages
used for applications).
Looking at this problem with kdb, I noticed that the CPU spends a lot
of time in swap_out(), even though there are no swap devices...
So...
mm/vmscan.c, replace swap_out with this:
static int swap_out(zone_t * classzone)
{
return 0;
}
Now, this might raise some eyebrows for those MM gurus reading this
mail but I assure you I've been doing this for a lot of time (and
a lot of machines) on 2.4.27, and it took care of my kswapd issues
quite nicely.
I hope it helps...
--
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il
next prev parent reply other threads:[~2007-04-01 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c9aa5d00703310110s2a21f19l37544c3d46be53c9@mail.gmail.com>
2007-03-31 8:11 ` Fwd: kswapd issues + kernel 2.4.21-32.0.1.ELsmp Pedram M
2007-03-31 15:50 ` Rik van Riel
2007-04-01 10:21 ` Dan Aloni [this message]
[not found] <fa.vikcLJfO/FKczN77bSVCqEtBhL0@ifi.uio.no>
[not found] ` <fa.Fyq10Ks5ejO6P+77Y8svOle1kro@ifi.uio.no>
2007-04-01 20:27 ` Robert Hancock
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=20070401102127.GA16987@localdomain \
--to=da-x@monatomic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmessri@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox