From: Mel Gorman <mgorman@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Max Asbock <masbock@linux.vnet.ibm.com>,
mingo@redhat.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [Patch] tracing: tell mm_migrate_pages event about numa_misplaced
Date: Mon, 23 Jun 2014 15:56:32 +0100 [thread overview]
Message-ID: <20140623145632.GQ10819@suse.de> (raw)
In-Reply-To: <20140623103111.00197f5d@gandalf.local.home>
On Mon, Jun 23, 2014 at 10:31:11AM -0400, Steven Rostedt wrote:
> On Mon, 23 Jun 2014 15:21:59 +0100
> Mel Gorman <mgorman@suse.de> wrote:
>
> > On Fri, Jun 20, 2014 at 11:49:16AM -0700, Max Asbock wrote:
> > >
> > > The mm_migrate_pages trace event reports a reason for the migration, typically as a
> > > symbolic string. The exception is the reason MR_NUMA_MISPLACED for which it just displays
> > > the numeric value:
> > > mm_migrate_pages: nr_succeeded=1 nr_failed=0 mode=MIGRATE_ASYNC reason=0x5
> > >
> > > This patch makes the output consistent by introducing a string value for MR_NUMA_MISPLACED.
> > > The event is then reported as:
> > > mm_migrate_pages: nr_succeeded=1 nr_failed=0 mode=MIGRATE_ASYNC reason=numa_misplaced
> > >
> > > Signed-off-by: Max Asbock <masbock@linux.vnet.ibm.com>
> >
> > Acked-by: Mel Gorman <mgorman@suse.de>
> >
>
> Would you like to take this? Or Andrew?
>
I expect Andrew will pick it up.
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2014-06-23 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 18:49 [Patch] tracing: tell mm_migrate_pages event about numa_misplaced Max Asbock
2014-06-23 14:21 ` Mel Gorman
2014-06-23 14:31 ` Steven Rostedt
2014-06-23 14:56 ` Mel Gorman [this message]
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=20140623145632.GQ10819@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masbock@linux.vnet.ibm.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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.