From: Wu Fengguang <fengguang.wu@intel.com>
To: jack marrow <jackmarrow2@gmail.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: Thu, 12 Mar 2009 15:59:52 +0800 [thread overview]
Message-ID: <20090312075952.GA19331@localhost> (raw)
In-Reply-To: <e2dc2c680903120053w37968c1cy556812cef63f0896@mail.gmail.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?
WARNING: multiple messages have this Message-ID (diff)
From: Wu Fengguang <fengguang.wu@intel.com>
To: jack marrow <jackmarrow2@gmail.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: Thu, 12 Mar 2009 15:59:52 +0800 [thread overview]
Message-ID: <20090312075952.GA19331@localhost> (raw)
In-Reply-To: <e2dc2c680903120053w37968c1cy556812cef63f0896@mail.gmail.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?
--
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:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 10:41 Memory usage per memory zone jack marrow
2009-03-11 11:43 ` Wu Fengguang
2009-03-11 11:43 ` Wu Fengguang
2009-03-11 11:51 ` jack marrow
2009-03-11 11:51 ` jack marrow
2009-03-11 12:11 ` Wu Fengguang
2009-03-11 12:11 ` Wu Fengguang
2009-03-11 12:16 ` jack marrow
2009-03-11 12:16 ` jack marrow
2009-03-11 12:26 ` Wu Fengguang
2009-03-11 12:26 ` Wu Fengguang
2009-03-12 7:53 ` jack marrow
2009-03-12 7:53 ` jack marrow
2009-03-12 7:59 ` Wu Fengguang [this message]
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 8:48 ` jack marrow
2009-03-12 11:14 ` Wu Fengguang
2009-03-12 11:14 ` Wu Fengguang
2009-03-12 11:39 ` jack marrow
2009-03-12 11:39 ` jack marrow
[not found] ` <e2dc2c680903120117j7be962b2xd63f3296f8f65a46@mail.gmail.com>
2009-03-12 10:38 ` Wu Fengguang
2009-03-12 10:38 ` Wu Fengguang
2009-03-12 11:38 ` jack marrow
2009-03-12 11:38 ` jack marrow
2009-03-12 11:48 ` jack marrow
2009-03-12 11:48 ` jack marrow
2009-03-12 12:06 ` Wu Fengguang
2009-03-12 12:06 ` Wu Fengguang
2009-03-12 11:51 ` Wu Fengguang
2009-03-12 11:51 ` Wu Fengguang
2009-03-12 12:01 ` jack marrow
2009-03-12 12:01 ` jack marrow
2009-03-11 13:39 ` Thomas Schoebel-Theuer
2009-03-11 15:06 ` 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=20090312075952.GA19331@localhost \
--to=fengguang.wu@intel.com \
--cc=jackmarrow2@gmail.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 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.