From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Christoph Lameter <cl@linux-foundation.org>,
Rik van Riel <riel@redhat.com>
Subject: [PATCH 0/4] OOM analysis helper patch series v3
Date: Mon, 13 Jul 2009 14:57:25 +0900 (JST) [thread overview]
Message-ID: <20090713144924.6257.A69D9226@jp.fujitsu.com> (raw)
ChangeLog
Since v2
- Dropped "[4/5] add isolate pages vmstat" temporary because it become
slightly big. Then, I plan to submit it as another patchset.
- Rewrote many patch description (Thanks! Christoph)
Since v1
- Dropped "[5/5] add NR_ANON_PAGES to OOM log" patch
- Instead, introduce "[5/5] add shmem vmstat" patch
- Fixed unit bug (Thanks Minchan)
- Separated isolated vmstat to two field (Thanks Minchan and Wu)
- Fixed isolated page and lumpy reclaim issue (Thanks Minchan)
- Rewrote some patch description (Thanks Christoph)
This patch series are tested on 2.6.31-rc2 + mm-show_free_areas-display-slab-pages-in-two-separate-fields.patch
==========================
Current OOM log doesn't provide sufficient memory usage information. it cause
make confusion to lkml MM guys.
this patch series add some memory usage information to OOM log output.
next reply other threads:[~2009-07-13 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 5:57 KOSAKI Motohiro [this message]
2009-07-13 6:00 ` [PATCH 1/4][resend] add per-zone statistics to show_free_areas() KOSAKI Motohiro
2009-07-13 6:01 ` [PATCH 2/4][resend] add buffer cache information " KOSAKI Motohiro
2009-07-13 6:02 ` [PATCH 3/4][resend] Show kernel stack usage in /proc/meminfo and OOM log output KOSAKI Motohiro
2009-07-13 22:29 ` Andrew Morton
2009-07-13 23:36 ` KOSAKI Motohiro
2009-07-13 6:05 ` [PATCH 4/4][resend] add shmem vmstat KOSAKI Motohiro
2009-07-13 20:47 ` [PATCH 0/4] OOM analysis helper patch series v3 Rik van Riel
2009-07-13 23:38 ` KOSAKI Motohiro
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=20090713144924.6257.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
/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®