From: Peter Zijlstra <peterz@infradead.org>
To: "Karol Šebesta" <sebesta.karol@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-admin@vger.kernel.org,
Rik van Riel <riel@redhat.com>
Subject: Re: extreme system load [kswapd]
Date: Tue, 20 Mar 2012 19:59:36 +0100 [thread overview]
Message-ID: <1332269976.18960.449.camel@twins> (raw)
In-Reply-To: <CA+pWcCZ28ByXuOu72FAAAQAPny3O0WDvd+vv1TryXw+9DMKwiA@mail.gmail.com>
On Tue, 2012-03-20 at 10:08 +0100, Karol Å ebesta wrote:
> We have a problem on our production machine with high CPU utilization
> caused by kswapd3 daemon. Server is 128GB of physical memory and 81GB
> of SWAP.
>
>
> # cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 5.6 (Tikanga)
That's a very very old kernel, I would suggest you upgrade to something
that has the reclaim rewrite Rik did to deal with large memory systems.
I think they're in RHEL6, but I'm sure Rik knows.
Also, since you're running this dinosaur, contact RHT, they're the only
ones that care about it -- but I guess you're going to get the same
suggestion.
next prev parent reply other threads:[~2012-03-20 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 9:08 extreme system load [kswapd] Karol Šebesta
2012-03-20 9:47 ` Nicolas Maupu
2012-03-20 18:59 ` Peter Zijlstra [this message]
2012-03-21 14:58 ` 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=1332269976.18960.449.camel@twins \
--to=peterz@infradead.org \
--cc=linux-admin@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=sebesta.karol@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;
as well as URLs for NNTP newsgroup(s).