From: Aaron Sowry <aaron@cendio.se>
To: linux-kernel@vger.kernel.org
Subject: Re: Help decoding oom-killer output
Date: Wed, 08 Sep 2010 10:54:56 +0200 [thread overview]
Message-ID: <4C874F60.4080901@cendio.se> (raw)
In-Reply-To: <4C8744D1.1010405@cendio.se>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
On 08/09/10 10:09, Aaron Sowry wrote:
> Since this change, oom-killer seems to think we are running out of
> memory, and starts killing arbitrary processes. Output from 'free' does
> not indicate any lack of memory resource:
...however I have just noticed that low memory allocation appears to be
somewhat stingy, given the total amount of RAM available:
tle-thn18:~ # cat /proc/meminfo
MemTotal: 37115096 kB
MemFree: 34528308 kB
Buffers: 49356 kB
Cached: 861024 kB
SwapCached: 0 kB
Active: 1830136 kB
Inactive: 549420 kB
Active(anon): 1442900 kB
Inactive(anon): 73056 kB
Active(file): 387236 kB
Inactive(file): 476364 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 36931780 kB
HighFree: 34520552 kB
LowTotal: 183316 kB
LowFree: 7756 kB
SwapTotal: 4200988 kB
SwapFree: 4200988 kB
Dirty: 2624 kB
Writeback: 0 kB
AnonPages: 1469264 kB
Mapped: 203692 kB
Shmem: 46780 kB
Slab: 95460 kB
SReclaimable: 31968 kB
SUnreclaim: 63492 kB
KernelStack: 9952 kB
PageTables: 31660 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 22758536 kB
Committed_AS: 4689664 kB
VmallocTotal: 524288 kB
VmallocUsed: 34520 kB
VmallocChunk: 311868 kB
HardwareCorrupted: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 8184 kB
DirectMap2M: 491520 kB
--
Aaron Sowry
Developer / Technical Sales
Cendio AB
Wallenbergs Gata 4
583 30 LINKÖPING
Sweden
aaron@cendio.se
Tel + 46 13 29 08 54
Fax + 46 13 21 47 00
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-09-08 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 8:09 Help decoding oom-killer output Aaron Sowry
2010-09-08 8:54 ` Aaron Sowry [this message]
2010-09-08 13:30 ` Andi Kleen
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=4C874F60.4080901@cendio.se \
--to=aaron@cendio.se \
--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 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.