From: Miaohe Lin <linmiaohe@huawei.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Naoya Horiguchi <nao.horiguchi@gmail.com>, <linux-mm@kvack.org>
Subject: Re: [PATCH v2 4/5] mm: migrate: add isolate_folio_to_list()
Date: Wed, 21 Aug 2024 10:00:30 +0800 [thread overview]
Message-ID: <5aa2f835-0337-d7d9-5ad2-1c5ca2d439d9@huawei.com> (raw)
In-Reply-To: <927205ab-bd83-4765-b2bb-3fd311f5ac6d@huawei.com>
On 2024/8/20 17:46, Kefeng Wang wrote:
>
>
> On 2024/8/20 17:32, Miaohe Lin wrote:
>> On 2024/8/17 16:49, Kefeng Wang wrote:
>>> Add isolate_folio_to_list() helper to try to isolate HugeTLB,
>>> no-LRU movable and LRU folios to a list, which will be reused by
>>> do_migrate_range() from memory hotplug soon, also drop the
>>> mf_isolate_folio() since we could directly use new helper in
>>> the soft_offline_in_use_page().
>>>
>>> Acked-by: David Hildenbrand <david@redhat.com>
>>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>>
>> Thanks for your patch.
>>>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index d8298017bd99..64a145a0e29f 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -2671,6 +2671,7 @@ static int soft_offline_in_use_page(struct page *page)
> struct folio *folio = page_folio(page);
> char const *msg_page[] = {"page", "hugepage"};
> bool huge = folio_test_hugetlb(folio);
> + bool isolated;
> LIST_HEAD(pagelist);
> struct migration_target_control mtc = {
> .nid = NUMA_NO_NODE,
> @@ -2710,7 +2711,18 @@ static int soft_offline_in_use_page(struct page *page)
> return 0;
> }
>
> - if (isolate_folio_to_list(folio, &pagelist)) {
> + isolated = isolate_folio_to_list(folio, &pagelist);
> +
> + /*
> + * If we succeed to isolate the folio, we grabbed another refcount on
> + * the folio, so we can safely drop the one we got from get_any_page().
> + * If we failed to isolate the folio, it means that we cannot go further
> + * and we will return an error, so drop the reference we got from
> + * get_any_page() as well.
> + */
> + folio_put(folio);
> +
> + if (isolated) {
> ret = migrate_pages(&pagelist, alloc_migration_target, NULL,
> (unsigned long)&mtc, MIGRATE_SYNC, MR_MEMORY_FAILURE, NULL);
> if (!ret) {
> @@ -2733,15 +2745,6 @@ static int soft_offline_in_use_page(struct page *page)
> ret = -EBUSY;
> }
>
> - /*
> - * If we succeed to isolate the folio, we grabbed another refcount on
> - * the folio, so we can safely drop the one we got from get_any_page().
> - * If we failed to isolate the folio, it means that we cannot go further
> - * and we will return an error, so drop the reference we got from
> - * get_any_page() as well.
> - */
> - folio_put(folio);
> -
> return ret;
> }
This works to me.
Thanks.
.
next prev parent reply other threads:[~2024-08-21 2:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 8:49 [PATCH resend v2 0/5] mm: memory_hotplug: improve do_migrate_range() Kefeng Wang
2024-08-17 8:49 ` [PATCH v2 1/5] mm: memory_hotplug: remove head variable in do_migrate_range() Kefeng Wang
2024-08-19 9:28 ` Jonathan Cameron
2024-08-19 10:41 ` Kefeng Wang
2024-08-21 7:33 ` Miaohe Lin
2024-08-26 14:42 ` David Hildenbrand
2024-08-17 8:49 ` [PATCH v2 2/5] mm: memory-failure: add unmap_posioned_folio() Kefeng Wang
2024-08-21 7:40 ` Miaohe Lin
2024-08-21 8:54 ` Kefeng Wang
2024-08-17 8:49 ` [PATCH v2 3/5] mm: memory_hotplug: check hwpoisoned page firstly in do_migrate_range() Kefeng Wang
2024-08-22 6:52 ` Miaohe Lin
2024-08-22 11:35 ` Kefeng Wang
2024-08-26 14:46 ` David Hildenbrand
2024-08-27 1:13 ` Kefeng Wang
2024-08-27 2:12 ` Miaohe Lin
2024-08-27 15:11 ` David Hildenbrand
2024-08-17 8:49 ` [PATCH v2 4/5] mm: migrate: add isolate_folio_to_list() Kefeng Wang
2024-08-20 9:32 ` Miaohe Lin
2024-08-20 9:46 ` Kefeng Wang
2024-08-21 2:00 ` Miaohe Lin [this message]
2024-08-21 2:14 ` Kefeng Wang
2024-08-22 6:56 ` Miaohe Lin
2024-08-26 14:50 ` David Hildenbrand
2024-08-27 1:19 ` Kefeng Wang
2024-08-17 8:49 ` [PATCH v2 5/5] mm: memory_hotplug: unify Huge/LRU/non-LRU movable folio isolation Kefeng Wang
2024-08-22 7:20 ` Miaohe Lin
2024-08-22 12:08 ` Kefeng Wang
2024-08-26 14:55 ` David Hildenbrand
2024-08-27 1:26 ` Kefeng Wang
2024-08-27 15:10 ` David Hildenbrand
2024-08-27 15:35 ` Kefeng Wang
2024-08-27 15:38 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2024-08-16 9:04 [PATCH v2 0/5] mm: memory_hotplug: improve do_migrate_range() Kefeng Wang
2024-08-16 9:04 ` [PATCH v2 4/5] mm: migrate: add isolate_folio_to_list() Kefeng Wang
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=5aa2f835-0337-d7d9-5ad2-1c5ca2d439d9@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--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