From: jack marrow <jackmarrow2@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Memory usage per memory zone
Date: Thu, 12 Mar 2009 09:48:42 +0100 [thread overview]
Message-ID: <e2dc2c680903120148j1aee0759td49055be059e33ae@mail.gmail.com> (raw)
In-Reply-To: <20090312081113.GA19506@localhost>
(Didn't reply all:)
2009/3/12 Wu Fengguang <fengguang.wu@intel.com>:
> On Thu, Mar 12, 2009 at 10:04:17AM +0200, jack marrow wrote:
>> 2009/3/12 Wu Fengguang <fengguang.wu@intel.com>:
>> > On Thu, Mar 12, 2009 at 09:53:27AM +0200, jack marrow wrote:
>> >> > Can you paste /proc/vmstat, /proc/meminfo, /proc/zoneinfo and
>> >> > /proc/slabinfo? Thank you.
>> >>
>> >> Sure, but I don't know if it will help.
>> >>
>> >> The oom info was from in the night, the rest is from now. I have no zoneinfo.
>> >>
>> >> http://pastebin.com/m67409bc0
>> >
>> > Thank you! So you are running a pretty old kernel?
>> >
>>
>> Yes. Kernel.2.6.9-78.
>>
>> Added more output from the other oom kills here:
>> http://pastebin.com/m76fc473d
>>
>> If I could just find a way to find out what is using up all the memory
>> in a zone I could go away happy :)
>
> But the highmem zone wont help you much, since you have a large 900M
> normal zone and a tiny 100M highmem zone ;)
>
> The cached files seem to be the memory killer:
I ran an echo 3 > drop_caches yesterday, I was hoping to come in and
find no oom kill. Oh well :)
I thought the kernel dropped caches if a program needs the ram?
>
> MemTotal: 1034496 kB
> MemFree: 95600 kB
> Buffers: 49916 kB
> Cached: 761544 kB
> SwapCached: 0 kB
> Active: 80484 kB
> Inactive: 749960 kB
> HighTotal: 131008 kB
> HighFree: 68480 kB
> LowTotal: 903488 kB
> LowFree: 27120 kB
> SwapTotal: 2040212 kB
> SwapFree: 2039780 kB
> Dirty: 4 kB
> Writeback: 0 kB
> Mapped: 32636 kB
> Slab: 93856 kB
> CommitLimit: 2557460 kB
> Committed_AS: 129980 kB
> PageTables: 1800 kB
> VmallocTotal: 106488 kB
> VmallocUsed: 3372 kB
> VmallocChunk: 102616 kB
> HugePages_Total: 0
> HugePages_Free: 0
> Hugepagesize: 2048 kB
>
> Is upgrading the kernel an option for you?
No :(
I think shoving some more ram in the box is the best doable option.
Would this help here?
To do that I need to say "look at how much cache we are using for
files, that cache is in the high mem zone (look here) so let's put
some more ram in". Does the cache always live in the high mem zone?
>
> Thanks,
> Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-12 8:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e2dc2c680903110341g6c9644b8j87ce3b364807e37f@mail.gmail.com>
2009-03-11 11:43 ` Wu Fengguang
2009-03-11 11:51 ` jack marrow
2009-03-11 12:11 ` Wu Fengguang
2009-03-11 12:16 ` jack marrow
2009-03-11 12:26 ` Wu Fengguang
2009-03-12 7:53 ` jack marrow
2009-03-12 7:59 ` Wu Fengguang
[not found] ` <e2dc2c680903120104h4d19a3f6j57ad045bc06f9a90@mail.gmail.com>
[not found] ` <20090312081113.GA19506@localhost>
2009-03-12 8:48 ` jack marrow [this message]
2009-03-12 11:14 ` Wu Fengguang
2009-03-12 11:39 ` jack marrow
[not found] ` <e2dc2c680903120117j7be962b2xd63f3296f8f65a46@mail.gmail.com>
2009-03-12 10:38 ` Wu Fengguang
2009-03-12 11:38 ` jack marrow
2009-03-12 11:48 ` jack marrow
2009-03-12 12:06 ` Wu Fengguang
2009-03-12 11:51 ` Wu Fengguang
2009-03-12 12:01 ` jack marrow
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=e2dc2c680903120148j1aee0759td49055be059e33ae@mail.gmail.com \
--to=jackmarrow2@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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