From: jack marrow <jackmarrow2@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "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: Wed, 11 Mar 2009 13:16:38 +0100 [thread overview]
Message-ID: <e2dc2c680903110516v2c66d4a4h6a422cffceb12e2@mail.gmail.com> (raw)
In-Reply-To: <20090311121123.GA7656@localhost>
2009/3/11 Wu Fengguang <fengguang.wu@intel.com>:
> On Wed, Mar 11, 2009 at 01:51:32PM +0200, jack marrow wrote:
>> 2009/3/11 Wu Fengguang <fengguang.wu@intel.com>:
>> > Hi jack,
>> >
>> > On Wed, Mar 11, 2009 at 11:41:43AM +0100, jack marrow wrote:
>> >> Hello,
>> >>
>> >> I have a box where the oom-killer is killing processes due to running
>> >> out of memory in zone_normal. I can see using slabtop that the inode
>> >
>> > How do you know that the memory pressure on zone normal stand out alone?
>>
>> For the normal zone only, I see "all_unreclaimable: yes" and 3 megs of free ram:
>>
>> kernel: Normal free:2576kB min:3728kB low:7456kB high:11184kB
>> active:1304kB inactive:128kB present:901120kB pages_scanned:168951
>> all_unreclaimable? yes
>
> It's normal behavior. Linux kernel tries hard to utilize most of
> the free memory for caching files :)
With all_unreclaimable = yes is normal?
>
>> >> caches are using up lots of memory and guess this is the problem, so
>> >> have cleared them using an echo to drop_caches.
>> >
>> > It would better be backed by concrete numbers...
>> >
>> >>
>> >> I would quite like to not guess though - is it possible to use slabtop
>> >> (or any other way) to view ram usage per zone so I can pick out the
>> >> culprit?
>> >
>> > /proc/zoneinfo and /proc/vmstat do have some per-zone numbers.
>> > Some of them deal with slabs.
>>
>> Thanks, I'll read up on how to interpret these.
>>
>> Do you recommend these two files for tracking down memory usage per
>> process per zone?
>
> No, the two interfaces provide system wide counters. We have the well
> known tools "ps" and "top" for per-process numbers, hehe.
ps and top do not have per-zone numbers. How do I get those?
>
> 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-11 12:16 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 [this message]
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
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=e2dc2c680903110516v2c66d4a4h6a422cffceb12e2@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