From: Mel Gorman <mgorman@suse.de>
To: Linux-MM <linux-mm@kvack.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/5] vmstats for compaction, migration and autonuma
Date: Mon, 22 Oct 2012 08:59:46 +0100 [thread overview]
Message-ID: <1350892791-2682-1-git-send-email-mgorman@suse.de> (raw)
I'm travelling for a conference at the moment so these patches are not
tested but with the ongoing NUMA migration work I figured it was best to
post these sooner rather than later.
This series adds vmstat counters and tracepoints for migration, compaction
and autonuma. Using them it's possible to create a basic cost model to
estimate the overhead due to compaction or autonuma. Using the stats it
is also possible to measure if a workload is converging on autonuma or
not and potentially measure how quickly it is converging.
Ideally the same stats would be available for schednuma but I did not
review the series when it was last posted in July and had not seen a
recent posting. I only recently heard they were in the -tip tree but will
not get the chance to look at them until I've finished travelling in a
weeks time. If schednuma had similar stats it would then be possible to
compare schednuma and autonuma in terms of how quickly a workload converges
with either approach.
include/linux/migrate.h | 14 +++++++++-
include/linux/vm_event_item.h | 12 ++++++++-
include/trace/events/migrate.h | 52 ++++++++++++++++++++++++++++++++++++++++
mm/autonuma.c | 22 +++++++++++++----
mm/compaction.c | 15 +++++++----
mm/memory-failure.c | 3 +-
mm/memory_hotplug.c | 3 +-
mm/mempolicy.c | 6 +++-
mm/migrate.c | 16 ++++++++++-
mm/page_alloc.c | 3 +-
mm/vmstat.c | 16 ++++++++++--
11 files changed, 139 insertions(+), 23 deletions(-)
create mode 100644 include/trace/events/migrate.h
--
1.7.7
--
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 reply other threads:[~2012-10-22 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 7:59 Mel Gorman [this message]
2012-10-22 7:59 ` [PATCH 1/5] mm: compaction: Move migration fail/success stats to migrate.c Mel Gorman
2012-10-25 2:57 ` David Rientjes
2012-10-22 7:59 ` [PATCH 2/5] mm: migrate: Add a tracepoint for migrate_pages Mel Gorman
2012-10-22 8:05 ` [PATCH 3/5] mm: compaction: Add scanned and isolated counters for compaction Mel Gorman
2012-10-22 8:06 ` [PATCH 4/5] mm: autonuma: Add pte updates, hinting and migration stats for AutoNUMA Mel Gorman
2012-10-22 8:06 ` [PATCH 5/5] mm: autonuma: Specify the migration reason for the tracepoint Mel Gorman
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=1350892791-2682-1-git-send-email-mgorman@suse.de \
--to=mgorman@suse.de \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).