From: Stefan Lankes <lankes@lfbs.rwth-aachen.de>
To: linux-kernel@vger.kernel.org
Subject: [RFC PATCH 4/4]: affinity-on-next-touch
Date: Mon, 11 May 2009 10:27:37 +0200 [thread overview]
Message-ID: <001001c9d212$57d1eeb0$0775cc10$@rwth-aachen.de> (raw)
[Patch 4/4]: This part of the patch adds some counters to detect migration
errors and publishes these counters via /proc/vmstat. Besides this, the
Kconfig file is extend with the parameter CONFIG_AFFINITY_ON_NEXT_TOUCH.
include/linux/vmstat.h | 6 ++++++
mm/Kconfig | 9 +++++++++
mm/vmstat.c | 6 ++++++
3 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/include/linux/vmstat.h b/include/linux/vmstat.h
index 524cd1b..64c8e66 100644
--- a/include/linux/vmstat.h
+++ b/include/linux/vmstat.h
@@ -51,6 +51,12 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
UNEVICTABLE_PGSTRANDED, /* unable to isolate on unlock */
UNEVICTABLE_MLOCKFREED,
#endif
+#ifdef CONFIG_AFFINITY_ON_NEXT_TOUCH
+ AONT_INVALID_NODEMASK,
+ AONT_ISOLATE_BUSY,
+ AONT_ISOLATE_FAILED,
+ AONT_MIGRATION_FAILED,
+#endif
NR_VM_EVENT_ITEMS
};
diff --git a/mm/Kconfig b/mm/Kconfig
index c2b57d8..025c328 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -181,6 +181,15 @@ config MIGRATION
example on NUMA systems to put pages nearer to the processors
accessing
the page.
+config AFFINITY_ON_NEXT_TOUCH
+ bool "Affinity on next touch (EXPERIMENTAL)" if (EXPERIMENTAL)
+ def_bool y
+ depends on MIGRATION
+ help
+ Allows the migration of pages to the node, which has the next
access
+ to the pages. This realized a page placement strategy, which is
called
+ "affinity-on-next-touch".
+
config PHYS_ADDR_T_64BIT
def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT
diff --git a/mm/vmstat.c b/mm/vmstat.c
index 66f6130..d0e9489 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -708,6 +708,12 @@ static const char * const vmstat_text[] = {
"unevictable_pgs_stranded",
"unevictable_pgs_mlockfreed",
#endif
+#ifdef CONFIG_AFFINITY_ON_NEXT_TOUCH
+ "aont_invalid_nodemask",
+ "aont_isolate_busy",
+ "aont_isolate_failed",
+ "aont_migration_failed",
+#endif
#endif
};
reply other threads:[~2009-05-11 8:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001001c9d212$57d1eeb0$0775cc10$@rwth-aachen.de' \
--to=lankes@lfbs.rwth-aachen.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®