From: "Andreas Grimm" <agrimm61@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Plenty of inactive memory
Date: Wed, 9 Apr 2008 13:19:22 +0200 [thread overview]
Message-ID: <cf40c6a90804090419o59bc215cw6068b7f2118efcfe@mail.gmail.com> (raw)
Hello everybody,
i got a weird problem with one of my servers. It's a Intel SR2500AL
with 32GB of RAM.
Looking at the memory usage of the system, something is going totally
wrong. The crucial numbers from /proc/meminfo are:
MemTotal: 33265916 kB
MemFree: 416168 kB
Inactive: 24630428 kB (24GB? whooaaa)
Another system with only 16GB, same amount of users and load, shows a
more normal behaviour:
MemTotal: 16619808 kB
MemFree: 6912676 kB
Inactive: 1774364 kB
Why does the 32GB-System have this plenty of inactive memory. Is there
a way to find out, what the kernel is holding in readiness?
OS: SLES 10 SP1
Kernel : 2.6.16.27-0.9-bigsmp
Thanks in advance.
Andreas Grimm
next reply other threads:[~2008-04-09 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 11:19 Andreas Grimm [this message]
[not found] <fa.HIr5TAepu3mcAI6oLfBPL3wGwss@ifi.uio.no>
2008-04-09 14:31 ` 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=cf40c6a90804090419o59bc215cw6068b7f2118efcfe@mail.gmail.com \
--to=agrimm61@gmail.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
all inboxes | Powered by JetHome®