From: Andre Margis <andre@sam.com.br>
To: linux-kernel@vger.kernel.org
Subject: kswapd kernel 2.4.9
Date: Wed, 3 Oct 2001 08:39:20 -0300 [thread overview]
Message-ID: <200110031143.IAA16823@inter.lojasrenner.com.br> (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.
my /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 1957650432 1946705920 10944512 0 392224768 1218093056
Swap: 1073733632 684032 1073049600
MemTotal: 10300376 kB
MemFree: 10688 kB
MemShared: 0 kB
Buffers: 383032 kB
Cached: 9577652 kB
SwapCached: 500 kB
Active: 3328980 kB
Inact_dirty: 6628180 kB
Inact_clean: 4088 kB
Inact_target: 8 kB
HighTotal: 9568256 kB
HighFree: 3948 kB
LowTotal: 732120 kB
LowFree: 6740 kB
SwapTotal: 1048568 kB
SwapFree: 1047900 kB
This is normal?
Thank's
Andre
next reply other threads:[~2001-10-03 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 11:39 Andre Margis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 13:22 kswapd kernel 2.4.9 cwright
2001-10-03 13:27 ` 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=200110031143.IAA16823@inter.lojasrenner.com.br \
--to=andre@sam.com.br \
--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