linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, k.kozlowski@samsung.com,
	Seth Jennings <sjenning@linux.vnet.ibm.com>,
	Mel Gorman <mgorman@suse.de>,
	guz.fnst@cn.fujitsu.com, Benjamin LaHaise <bcrl@kvack.org>,
	Dave Hansen <dave.hansen@intel.com>,
	lliubbo@gmail.com, aquini@redhat.com,
	Rik van Riel <riel@redhat.com>, Minchan Kim <minchan@kernel.org>
Subject: [RFC 1/3] mm: Introduce new page flag
Date: Tue, 13 Aug 2013 16:05:00 +0900	[thread overview]
Message-ID: <1376377502-28207-2-git-send-email-minchan@kernel.org> (raw)
In-Reply-To: <1376377502-28207-1-git-send-email-minchan@kernel.org>

Signed-off-by: Minchan Kim <minchan@kernel.org>
---
 include/linux/page-flags.h |    2 ++
 mm/page_alloc.c            |    1 +
 2 files changed, 3 insertions(+)

diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
index 6d53675..75ce843 100644
--- a/include/linux/page-flags.h
+++ b/include/linux/page-flags.h
@@ -109,6 +109,7 @@ enum pageflags {
 #ifdef CONFIG_TRANSPARENT_HUGEPAGE
 	PG_compound_lock,
 #endif
+	PG_pin,
 	__NR_PAGEFLAGS,
 
 	/* Filesystems */
@@ -197,6 +198,7 @@ struct page;	/* forward declaration */
 
 TESTPAGEFLAG(Locked, locked)
 PAGEFLAG(Error, error) TESTCLEARFLAG(Error, error)
+PAGEFLAG(Pin, pin) TESTCLEARFLAG(Pin, pin)
 PAGEFLAG(Referenced, referenced) TESTCLEARFLAG(Referenced, referenced)
 PAGEFLAG(Dirty, dirty) TESTSCFLAG(Dirty, dirty) __CLEARPAGEFLAG(Dirty, dirty)
 PAGEFLAG(LRU, lru) __CLEARPAGEFLAG(LRU, lru)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index b100255..5dd8b43 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -6345,6 +6345,7 @@ static const struct trace_print_flags pageflag_names[] = {
 #ifdef CONFIG_TRANSPARENT_HUGEPAGE
 	{1UL << PG_compound_lock,	"compound_lock"	},
 #endif
+	{1UL << PG_pin,			"pin"		},
 };
 
 static void dump_page_flags(unsigned long flags)
-- 
1.7.9.5

--
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>

  reply	other threads:[~2013-08-13  7:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13  7:04 [RFC 0/3] Pin page control subsystem Minchan Kim
2013-08-13  7:05 ` Minchan Kim [this message]
2013-08-13  7:05 ` [RFC 2/3] pinpage " Minchan Kim
2013-08-13  7:05 ` [RFC 3/3] mm: migrate pinned page Minchan Kim
2013-08-13  9:46 ` [RFC 0/3] Pin page control subsystem Krzysztof Kozlowski
2013-08-13 14:23   ` Benjamin LaHaise
2013-08-14  0:08     ` Minchan Kim
2013-08-13 23:54   ` Minchan Kim
2013-08-13 16:21 ` Christoph Lameter
2013-08-14  0:12   ` Minchan Kim
2013-08-14 16:36     ` Christoph Lameter
2013-08-14 16:47       ` Minchan Kim
2013-08-14 16:58         ` Christoph Lameter
2013-08-15  4:48           ` Minchan Kim
2013-08-15 15:18             ` Christoph Lameter

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=1376377502-28207-2-git-send-email-minchan@kernel.org \
    --to=minchan@kernel.org \
    --cc=aquini@redhat.com \
    --cc=bcrl@kvack.org \
    --cc=dave.hansen@intel.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=mgorman@suse.de \
    --cc=riel@redhat.com \
    --cc=sjenning@linux.vnet.ibm.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).