From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/3] thp: introduce khugepaged_cleanup_page
Date: Wed, 12 Sep 2012 20:57:23 +0800 [thread overview]
Message-ID: <505086B3.6070603@linux.vnet.ibm.com> (raw)
In-Reply-To: <50508632.9090003@linux.vnet.ibm.com>
It is used to release the page on the fail path, then the page need not
be cleaned up in khugepaged_prealloc_page anymore
Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
---
mm/huge_memory.c | 19 +++++++++++++++----
1 files changed, 15 insertions(+), 4 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 5622347..de0a028 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -1827,9 +1827,6 @@ static bool khugepaged_prealloc_page(struct page **hpage, bool *wait)
*wait = false;
*hpage = NULL;
khugepaged_alloc_sleep();
- } else if (*hpage) {
- put_page(*hpage);
- *hpage = NULL;
}
return true;
@@ -1863,6 +1860,13 @@ static struct page
count_vm_event(THP_COLLAPSE_ALLOC);
return *hpage;
}
+
+static void khugepaged_cleanup_page(struct page **hpage)
+{
+ VM_BUG_ON(!*hpage);
+ put_page(*hpage);
+ *hpage = NULL;
+}
#else
static struct page *khugepaged_alloc_hugepage(bool *wait)
{
@@ -1903,6 +1907,10 @@ static struct page
VM_BUG_ON(!*hpage);
return *hpage;
}
+
+static void khugepaged_cleanup_page(struct page **hpage)
+{
+}
#endif
static void collapse_huge_page(struct mm_struct *mm,
@@ -1936,8 +1944,10 @@ static void collapse_huge_page(struct mm_struct *mm,
if (!new_page)
return;
- if (unlikely(mem_cgroup_newpage_charge(new_page, mm, GFP_KERNEL)))
+ if (unlikely(mem_cgroup_newpage_charge(new_page, mm, GFP_KERNEL))) {
+ khugepaged_cleanup_page(hpage);
return;
+ }
/*
* Prevent all access to pagetables with the exception of
@@ -2048,6 +2058,7 @@ out_up_write:
return;
out:
+ khugepaged_cleanup_page(hpage);
mem_cgroup_uncharge_page(new_page);
goto out_up_write;
}
--
1.7.7.6
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/3] thp: introduce khugepaged_cleanup_page
Date: Wed, 12 Sep 2012 20:57:23 +0800 [thread overview]
Message-ID: <505086B3.6070603@linux.vnet.ibm.com> (raw)
In-Reply-To: <50508632.9090003@linux.vnet.ibm.com>
It is used to release the page on the fail path, then the page need not
be cleaned up in khugepaged_prealloc_page anymore
Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
---
mm/huge_memory.c | 19 +++++++++++++++----
1 files changed, 15 insertions(+), 4 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 5622347..de0a028 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -1827,9 +1827,6 @@ static bool khugepaged_prealloc_page(struct page **hpage, bool *wait)
*wait = false;
*hpage = NULL;
khugepaged_alloc_sleep();
- } else if (*hpage) {
- put_page(*hpage);
- *hpage = NULL;
}
return true;
@@ -1863,6 +1860,13 @@ static struct page
count_vm_event(THP_COLLAPSE_ALLOC);
return *hpage;
}
+
+static void khugepaged_cleanup_page(struct page **hpage)
+{
+ VM_BUG_ON(!*hpage);
+ put_page(*hpage);
+ *hpage = NULL;
+}
#else
static struct page *khugepaged_alloc_hugepage(bool *wait)
{
@@ -1903,6 +1907,10 @@ static struct page
VM_BUG_ON(!*hpage);
return *hpage;
}
+
+static void khugepaged_cleanup_page(struct page **hpage)
+{
+}
#endif
static void collapse_huge_page(struct mm_struct *mm,
@@ -1936,8 +1944,10 @@ static void collapse_huge_page(struct mm_struct *mm,
if (!new_page)
return;
- if (unlikely(mem_cgroup_newpage_charge(new_page, mm, GFP_KERNEL)))
+ if (unlikely(mem_cgroup_newpage_charge(new_page, mm, GFP_KERNEL))) {
+ khugepaged_cleanup_page(hpage);
return;
+ }
/*
* Prevent all access to pagetables with the exception of
@@ -2048,6 +2058,7 @@ out_up_write:
return;
out:
+ khugepaged_cleanup_page(hpage);
mem_cgroup_uncharge_page(new_page);
goto out_up_write;
}
--
1.7.7.6
next prev parent reply other threads:[~2012-09-12 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 12:55 [PATCH 0/3] thp: tidy and fix khugepaged_prealloc_page Xiao Guangrong
2012-09-12 12:55 ` Xiao Guangrong
2012-09-12 12:56 ` [PATCH 1/3] thp: fix forgetting to reset the page alloc indicator Xiao Guangrong
2012-09-12 12:56 ` Xiao Guangrong
2012-09-12 12:56 ` [PATCH 2/3] thp: move release mmap_sem lock out of khugepaged_alloc_page Xiao Guangrong
2012-09-12 12:56 ` Xiao Guangrong
2012-09-12 22:18 ` Andrew Morton
2012-09-12 22:18 ` Andrew Morton
2012-09-13 9:16 ` Xiao Guangrong
2012-09-13 9:16 ` Xiao Guangrong
2012-09-12 12:57 ` Xiao Guangrong [this message]
2012-09-12 12:57 ` [PATCH 3/3] thp: introduce khugepaged_cleanup_page Xiao Guangrong
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=505086B3.6070603@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.