From: <cwright@softpixel.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kswapd kernel 2.4.9
Date: Wed, 3 Oct 2001 09:22:57 -0400 (EDT) [thread overview]
Message-ID: <30402.205.188.199.21.1002115377@webmail.softpixel.com> (raw)
> I\'m running kernel 2.4.9 under a DELL 8450 with 8xP-III and 10GB RAM.
> Yesterday a run a BIG I/O, and when this process run, my cached goes to
9GB
> and the kswapd is using 100% of one cpu after that.
did it stay at 100%, or did it ease up slightly afterward?
I have noticed a similar problem with ancient kernels (2.0.0) and not quite
as ancient one (2.2.19) where certain applications cause all your physical
ram to be used, then all the cache. after its all used (for some mystery
purpose?) it goes back to normal. maybe my boxes are just flukes though
chris
next reply other threads:[~2001-10-03 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 13:22 cwright [this message]
2001-10-03 13:27 ` kswapd kernel 2.4.9 Andre Margis
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 11:39 Andre Margis
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=30402.205.188.199.21.1002115377@webmail.softpixel.com \
--to=cwright@softpixel.com \
--cc=linux-kernel@vger.kernel.org \
/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