From: "Jan Kundrát" <jkt@gentoo.org>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kswapd high CPU usage with no swap
Date: Thu, 27 Sep 2007 00:37:00 +0200 [thread overview]
Message-ID: <46FADF0C.7000808@gentoo.org> (raw)
In-Reply-To: <20070926112510.314e8775@cuia.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
>> When this is sorted out, should I keep the previous patch [1] applied
>> as well?
>
> That doesn't hurt.
OK, I've used just the latter patch (because I somehow believe the first
one lowers the probability of bad behavior), so let's see if kswapd
consumes CPU again. I don't have any test patter to trigger that CPU
usage, though...
Cheers and thanks for your time,
-jkt
--
cd /local/pub && more beer > /dev/mouth
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-09-26 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 0:13 kswapd high CPU usage with no swap Jan Kundrát
2007-09-25 2:34 ` Rik van Riel
2007-09-25 10:13 ` Jan Kundrát
2007-09-26 1:31 ` Rik van Riel
2007-09-26 7:27 ` Jan Kundrát
2007-09-26 15:25 ` Rik van Riel
2007-09-26 22:37 ` Jan Kundrát [this message]
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=46FADF0C.7000808@gentoo.org \
--to=jkt@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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.