From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Tony Luck <tony.luck@intel.com>,
gong.chen@linux.intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] mm/hwpoison: don't need to hold compound lock for hugetlbfs page
Date: Thu, 22 Aug 2013 11:52:52 -0400 [thread overview]
Message-ID: <1377186772-rb1um2cz-mutt-n-horiguchi@ah.jp.nec.com> (raw)
In-Reply-To: <1377164907-24801-2-git-send-email-liwanp@linux.vnet.ibm.com>
On Thu, Aug 22, 2013 at 05:48:23PM +0800, Wanpeng Li wrote:
> compound lock is introduced by commit e9da73d67("thp: compound_lock."),
> it is used to serialize put_page against __split_huge_page_refcount().
> In addition, transparent hugepages will be splitted in hwpoison handler
> and just one subpage will be poisoned. There is unnecessary to hold
> compound lock for hugetlbfs page. This patch replace compound_trans_order
> by compond_order in the place where the page is hugetlbfs page.
>
> Signed-off-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>
> ---
> mm/memory-failure.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index 2c13aa7..5092e06 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -206,7 +206,7 @@ static int kill_proc(struct task_struct *t, unsigned long addr, int trapno,
> #ifdef __ARCH_SI_TRAPNO
> si.si_trapno = trapno;
> #endif
> - si.si_addr_lsb = compound_trans_order(compound_head(page)) + PAGE_SHIFT;
> + si.si_addr_lsb = compound_order(compound_head(page)) + PAGE_SHIFT;
>
> if ((flags & MF_ACTION_REQUIRED) && t == current) {
> si.si_code = BUS_MCEERR_AR;
> @@ -983,7 +983,7 @@ static int hwpoison_user_mappings(struct page *p, unsigned long pfn,
> static void set_page_hwpoison_huge_page(struct page *hpage)
> {
> int i;
> - int nr_pages = 1 << compound_trans_order(hpage);
> + int nr_pages = 1 << compound_order(hpage);
> for (i = 0; i < nr_pages; i++)
> SetPageHWPoison(hpage + i);
> }
> @@ -991,7 +991,7 @@ static void set_page_hwpoison_huge_page(struct page *hpage)
> static void clear_page_hwpoison_huge_page(struct page *hpage)
> {
> int i;
> - int nr_pages = 1 << compound_trans_order(hpage);
> + int nr_pages = 1 << compound_order(hpage);
> for (i = 0; i < nr_pages; i++)
> ClearPageHWPoison(hpage + i);
> }
> @@ -1491,7 +1491,7 @@ static int soft_offline_huge_page(struct page *page, int flags)
> } else {
> set_page_hwpoison_huge_page(hpage);
> dequeue_hwpoisoned_huge_page(hpage);
> - atomic_long_add(1 << compound_trans_order(hpage),
> + atomic_long_add(1 << compound_order(hpage),
> &num_poisoned_pages);
> }
> return ret;
> @@ -1551,7 +1551,7 @@ int soft_offline_page(struct page *page, int flags)
> if (PageHuge(page)) {
> set_page_hwpoison_huge_page(hpage);
> dequeue_hwpoisoned_huge_page(hpage);
> - atomic_long_add(1 << compound_trans_order(hpage),
> + atomic_long_add(1 << compound_order(hpage),
> &num_poisoned_pages);
> } else {
> SetPageHWPoison(page);
We have one more compound_trans_order() in unpoison_memory(), so could you
replace that too?
With that change ...
Reviewed-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Thanks,
Naoya Horiguchi
--
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 prev parent reply other threads:[~2013-08-22 15:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 9:48 [PATCH 1/6] mm/hwpoison: fix lose PG_dirty flag for errors on mlocked pages Wanpeng Li
2013-08-22 9:48 ` [PATCH 2/6] mm/hwpoison: don't need to hold compound lock for hugetlbfs page Wanpeng Li
2013-08-22 15:52 ` Naoya Horiguchi [this message]
2013-08-22 23:54 ` Wanpeng Li
2013-08-22 23:54 ` Wanpeng Li
2013-08-22 9:48 ` [PATCH 3/6] mm/hwpoison: fix num_poisoned_pages error statistics for thp Wanpeng Li
2013-08-22 16:43 ` Naoya Horiguchi
2013-08-22 17:00 ` Naoya Horiguchi
2013-08-22 23:52 ` Wanpeng Li
2013-08-22 23:52 ` Wanpeng Li
[not found] ` <5216a46f.a800310a.2351.ffffa95cSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-23 3:27 ` Naoya Horiguchi
2013-08-23 4:24 ` Wanpeng Li
2013-08-23 4:24 ` Wanpeng Li
2013-08-22 9:48 ` [PATCH 4/6] mm/hwpoison: don't set migration type twice to avoid hold heavy contend zone->lock Wanpeng Li
2013-08-22 19:06 ` Naoya Horiguchi
2013-08-23 0:15 ` Wanpeng Li
2013-08-23 0:15 ` Wanpeng Li
2013-08-22 9:48 ` [PATCH 5/6] mm/hwpoison: drop forward reference declarations __soft_offline_page() Wanpeng Li
2013-08-22 19:24 ` Naoya Horiguchi
2013-08-22 9:48 ` [PATCH 6/6] mm/hwpoison: centralize set PG_hwpoison flag and increase num_poisoned_pages Wanpeng Li
2013-08-22 20:13 ` Naoya Horiguchi
2013-08-23 0:03 ` Wanpeng Li
2013-08-23 0:03 ` Wanpeng Li
2013-08-22 15:51 ` [PATCH 1/6] mm/hwpoison: fix lose PG_dirty flag for errors on mlocked pages Naoya Horiguchi
2013-08-22 23:34 ` Wanpeng Li
2013-08-22 23:34 ` Wanpeng Li
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=1377186772-rb1um2cz-mutt-n-horiguchi@ah.jp.nec.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=tony.luck@intel.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