From: "Li, Ming Chun" <macli@brc.ubc.ca>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH 0/5] OOM analysis helper patch series v2
Date: Thu, 9 Jul 2009 15:05:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0907091502450.25351@mail.selltech.ca> (raw)
In-Reply-To: <alpine.DEB.1.00.0907091038380.22613@mail.selltech.ca>
On Thu, 9 Jul 2009, Li, Ming Chun wrote:
I am applying the patch series to 2.6.31-rc2.
Vincent
> On Thu, 9 Jul 2009, KOSAKI Motohiro wrote:
>
> >
> > ChangeLog
> > Since v1
> > - Droped "[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)
> >
> >
> > 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.
> >
>
> Hi Kosaki,
>
> Sorry this is slightly off topic, I am newbie and want to test out your
> patch series. I am using alpine as email client to save your patches to
> /usr/src/linux-2.6/patches:
>
> #ls -l /usr/src/linux-2.6/patches/
>
> -rw------- 1 root src 6682 2009-07-09 10:24 km1.patch
> -rw------- 1 root src 6980 2009-07-09 10:24 km2.patch
> -rw------- 1 root src 9871 2009-07-09 10:24 km3.patch
> -rw------- 1 root src 12539 2009-07-09 10:24 km4.patch
> -rw------- 1 root src 11499 2009-07-09 10:24 km5.patch
>
> Then I apply your patches using git-am, I got:
>
> ---------------
> /usr/src/linux-2.6# git checkout experimental
> Switched to branch "experimental"
>
> /usr/src/linux-2.6# git am ./patches/km1.patch
> Applying add per-zone statistics to show_free_areas()
>
> /usr/src/linux-2.6# git am ./patches/km2.patch
> Applying add buffer cache information to show_free_areas()
> error: patch failed: mm/page_alloc.c:2118
> error: mm/page_alloc.c: patch does not apply
> Patch failed at 0002.
> When you have resolved this problem run "git-am --resolved".
> If you would prefer to skip this patch, instead run "git-am --skip".
>
> /usr/src/linux-2.6# git am ./patches/km3.patch
> previous dotest directory .dotest still exists but mbox given.
>
> /usr/src/linux-2.6# rm -rf .dotest/
>
> /usr/src/linux-2.6# git am ./patches/km3.patch
> Applying Show kernel stack usage to /proc/meminfo and OOM log
>
> /usr/src/linux-2.6# git am ./patches/km4.patch
> Applying add isolate pages vmstat
> error: patch failed: mm/page_alloc.c:2115
> error: mm/page_alloc.c: patch does not apply
> Patch failed at 0002.
> When you have resolved this problem run "git-am --resolved".
> If you would prefer to skip this patch, instead run "git-am --skip".
>
> /usr/src/linux-2.6# git am ./patches/km5.patch
> previous dotest directory .dotest still exists but mbox given.
>
> /usr/src/linux-2.6# rm -rf .dotest/
>
> /usr/src/linux-2.6# git am ./patches/km5.patch
> Applying add shmem vmstat
> error: patch failed: include/linux/mmzone.h:102
> error: include/linux/mmzone.h: patch does not apply
> error: patch failed: mm/vmstat.c:646
> error: mm/vmstat.c: patch does not apply
> error: patch failed: mm/page_alloc.c:2120
> error: mm/page_alloc.c: patch does not apply
> Patch failed at 0002.
> When you have resolved this problem run "git-am --resolved".
> If you would prefer to skip this patch, instead run "git-am --skip".
> ------------
>
> Is there any better way that you could recommend to me to apply your
> patches cleanly? Thanks.
>
>
--
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-07-09 21:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 8:05 [PATCH 0/5] OOM analysis helper patch series v2 KOSAKI Motohiro
2009-07-09 8:06 ` [PATCH 1/5][resend] add per-zone statistics to show_free_areas() KOSAKI Motohiro
2009-07-09 10:14 ` Minchan Kim
2009-07-09 14:59 ` Rik van Riel
2009-07-09 8:11 ` [PATCH 2/5] add buffer cache information " KOSAKI Motohiro
2009-07-09 15:00 ` Rik van Riel
2009-07-09 20:37 ` Christoph Lameter
2009-07-09 23:39 ` KOSAKI Motohiro
2009-07-09 8:12 ` [PATCH 3/5][resend] Show kernel stack usage to /proc/meminfo and OOM log KOSAKI Motohiro
2009-07-09 10:20 ` Minchan Kim
2009-07-09 15:01 ` Rik van Riel
2009-07-09 20:38 ` Christoph Lameter
2009-07-09 8:14 ` [PATCH 4/5] add isolate pages vmstat KOSAKI Motohiro
2009-07-09 10:22 ` Minchan Kim
2009-07-09 20:43 ` Christoph Lameter
2009-07-10 2:11 ` KOSAKI Motohiro
2009-07-10 18:48 ` Christoph Lameter
2009-07-13 1:50 ` KOSAKI Motohiro
2009-07-09 8:18 ` [PATCH 5/5] add shmem vmstat KOSAKI Motohiro
2009-07-09 15:03 ` Rik van Riel
2009-07-09 20:46 ` Christoph Lameter
2009-07-10 1:23 ` Wu Fengguang
2009-07-09 10:41 ` [PATCH 0/5] OOM analysis helper patch series v2 Minchan Kim
2009-07-09 17:51 ` Li, Ming Chun
2009-07-09 22:05 ` Li, Ming Chun [this message]
2009-07-09 23:35 ` KOSAKI Motohiro
2009-07-10 2:17 ` KOSAKI Motohiro
2009-07-10 16:54 ` Li, Ming Chun
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=alpine.DEB.1.00.0907091502450.25351@mail.selltech.ca \
--to=macli@brc.ubc.ca \
--cc=kosaki.motohiro@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).