From: Ying Han <yinghan@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] Stack trace dedup
Date: Tue, 29 Mar 2011 18:32:58 -0700 [thread overview]
Message-ID: <BANLkTinDON4dV9ipZYJsxBW-bENMajw-wA@mail.gmail.com> (raw)
In-Reply-To: <20110330102205.E925.A69D9226@jp.fujitsu.com>
On Tue, Mar 29, 2011 at 6:21 PM, KOSAKI Motohiro
<kosaki.motohiro@jp.fujitsu.com> wrote:
>> This doesn't build.
>> ---
>> arch/x86/Kconfig | 3 +
>> arch/x86/include/asm/stacktrace.h | 2 +-
>> arch/x86/kernel/dumpstack.c | 5 +-
>> arch/x86/kernel/dumpstack_64.c | 10 +++-
>> arch/x86/kernel/stacktrace.c | 108 +++++++++++++++++++++++++++++++++++++
>> include/linux/sched.h | 10 +++-
>> init/main.c | 1 +
>> kernel/sched.c | 25 ++++++++-
>> 8 files changed, 154 insertions(+), 10 deletions(-)
>
> This is slightly reticence changelog. Can you please explain a purpose
> and benefit?
Hi:
Sorry about the spam. This is a patch that I was preparing to send
upstream but not ready yet. I don't know why it got sent out ( must be
myself did something wrong on my keyboard ) .
In a short, this eliminate the duplication of task stack trace in dump
messages. The problem w/ fixed size of dmesg ring buffer limits how
many task trace to be logged. When the duplication remains high, we
lose important information. This patch reduces the duplication by
dumping the first task stack trace only for contiguous duplications.
I will prepare it later with full commit description.
Thanks
--Ying
>
>
>
>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-30 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 17:28 [PATCH] Stack trace dedup Ying Han
2011-03-30 1:21 ` KOSAKI Motohiro
2011-03-30 1:32 ` Ying Han [this message]
2011-03-30 1:51 ` KOSAKI Motohiro
2011-03-30 2:32 ` Namhyung Kim
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=BANLkTinDON4dV9ipZYJsxBW-bENMajw-wA@mail.gmail.com \
--to=yinghan@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).