From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Oscar Salvador <osalvador@suse.de>,
Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>, <linux-mm@kvack.org>
Subject: Re: [PATCH v2 5/5] mm: memory_hotplug: unify Huge/LRU/non-LRU movable folio isolation
Date: Tue, 27 Aug 2024 23:35:24 +0800 [thread overview]
Message-ID: <eb5c41eb-8606-4f24-8d2d-1fb193f22278@huawei.com> (raw)
In-Reply-To: <fcef2c58-831c-4394-8bff-7b731591e8c5@redhat.com>
On 2024/8/27 23:10, David Hildenbrand wrote:
> On 27.08.24 03:26, Kefeng Wang wrote:
>>
>>
>> On 2024/8/26 22:55, David Hildenbrand wrote:
>>> On 17.08.24 10:49, Kefeng Wang wrote:
>>>> Use the isolate_folio_to_list() to unify hugetlb/LRU/non-LRU
>>>> folio isolation, which cleanup code a bit and save a few calls
>>>> to compound_head().
>>>>
>>>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>>>> ---
...
>>> Hm, remind me why we are changing the hugetlb code to not take a
>>> reference here? It does look odd.
>>
>> Different from folio_isolate_lru(), isolate_hugetlb() will check folio
>> and try get a reference of folio after get hugetlb_lock, other hugetlb
>> operation protected by this big lock too, so no need to take a reference
>> here.
>
> But this hugetlb-special casing looks quite ... special TBH.
>
> Is there no way to avoid it?
>
> I'd prefer something like the following, with a comment
>
> if (hugetlb)
> /*
> * We also want to migrate hugetlb folios that span multiple
> * memory blocks. So use whatever head page we identified.
> */
> folio = folio_try_get(folio);
> else
> folio = folio_get_nontail_page(page);
>
> if (!folio)
> continue;
>
>
> And then just dropping the reference unconditionally.
>
> Is there a problem with that? Optimizing for hugetlb references during
> migration is not worth the trouble.
>
>
> But now I wonder, why we not simply unconditionally do a folio_try_get()
Yes, I use folio_get_nontail_page() and folio_put() unconditionally in v1,
this will skip tail page, not consistent with previous behavior for
hugetlb, so I change to current way, but for migration, use
folio_try_get()/folio_put() is enough since we always migrate the whole
folio, it will be more simple. I will push an additional fix to v3,
which just sent a couple of hours ago.
[1]
https://lore.kernel.org/linux-mm/20240827114728.3212578-1-wangkefeng.wang@huawei.com/T/#t
next prev parent reply other threads:[~2024-08-27 15:35 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
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 [this message]
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 5/5] mm: memory_hotplug: unify Huge/LRU/non-LRU movable folio isolation 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=eb5c41eb-8606-4f24-8d2d-1fb193f22278@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
/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