From: Anshuman Khandual <anshuman.khandual@arm.com>
To: 20220830071514.GA1106752@hori.linux.bs1.fc.nec.co.jp,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>
Subject: Re: [PATCH v2] mm: memory-failure: kill __soft_offline_page()
Date: Thu, 1 Sep 2022 12:20:28 +0530 [thread overview]
Message-ID: <feb27c46-1713-ddf0-c3fb-fdaa68b7f191@arm.com> (raw)
In-Reply-To: <20220830104654.28234-1-wangkefeng.wang@huawei.com>
On 8/30/22 16:16, Kefeng Wang wrote:
> Squash the __soft_offline_page() into soft_offline_in_use_page() and kill
> __soft_offline_page().
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
> Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> v2: update hpage when try_to_split_thp_page() success
>
> mm/memory-failure.c | 25 ++++++++++---------------
> 1 file changed, 10 insertions(+), 15 deletions(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index b61f2de9f2a1..df54a6bc9bef 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -2434,11 +2434,11 @@ static bool isolate_page(struct page *page, struct list_head *pagelist)
> }
>
> /*
> - * __soft_offline_page handles hugetlb-pages and non-hugetlb pages.
> + * soft_offline_in_use_page handles hugetlb-pages and non-hugetlb pages.
> * If the page is a non-dirty unmapped page-cache page, it simply invalidates.
> * If the page is mapped, it migrates the contents over.
> */
> -static int __soft_offline_page(struct page *page)
> +static int soft_offline_in_use_page(struct page *page)
> {
> long ret = 0;
> unsigned long pfn = page_to_pfn(page);
> @@ -2451,6 +2451,14 @@ static int __soft_offline_page(struct page *page)
> .gfp_mask = GFP_USER | __GFP_MOVABLE | __GFP_RETRY_MAYFAIL,
> };
>
> + if (!huge && PageTransHuge(hpage)) {
> + if (try_to_split_thp_page(page)) {
> + pr_info("soft offline: %#lx: thp split failed\n", pfn);
> + return -EBUSY;
> + }
> + hpage = page;
> + }
> +
> lock_page(page);
> if (!PageHuge(page))
> wait_on_page_writeback(page);
> @@ -2500,19 +2508,6 @@ static int __soft_offline_page(struct page *page)
> return ret;
> }
>
> -static int soft_offline_in_use_page(struct page *page)
> -{
> - struct page *hpage = compound_head(page);
> -
> - if (!PageHuge(page) && PageTransHuge(hpage))
> - if (try_to_split_thp_page(page) < 0) {
> - pr_info("soft offline: %#lx: thp split failed\n",
> - page_to_pfn(page));
> - return -EBUSY;
> - }
> - return __soft_offline_page(page);
> -}
> -
> static void put_ref_page(struct page *page)
> {
> if (page)
prev parent reply other threads:[~2022-09-01 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 10:46 Kefeng Wang
2022-08-30 13:31 ` David Hildenbrand
2022-09-01 6:50 ` Anshuman Khandual [this message]
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=feb27c46-1713-ddf0-c3fb-fdaa68b7f191@arm.com \
--to=anshuman.khandual@arm.com \
--cc=20220830071514.GA1106752@hori.linux.bs1.fc.nec.co.jp \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=wangkefeng.wang@huawei.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