From: Mike Kravetz <mike.kravetz@oracle.com>
To: Michal Hocko <mhocko@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Muchun Song <songmuchun@bytedance.com>,
David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Matthew Wilcox <willy@infradead.org>,
Miaohe Lin <linmiaohe@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 2/5] hugetlb: convert page_huge_active() HPageMigratable flag
Date: Wed, 27 Jan 2021 15:27:21 -0800 [thread overview]
Message-ID: <1d05b4ae-e14d-794e-f2bb-0906cbfc2ba1@oracle.com> (raw)
In-Reply-To: <20210127102517.GG827@dhcp22.suse.cz>
On 1/27/21 2:25 AM, Michal Hocko wrote:
> On Fri 22-01-21 11:52:28, Mike Kravetz wrote:
>> Use the new hugetlb page specific flag HPageMigratable to replace the
>> page_huge_active interfaces. By it's name, page_huge_active implied
>> that a huge page was on the active list. However, that is not really
>> what code checking the flag wanted to know. It really wanted to determine
>> if the huge page could be migrated. This happens when the page is actually
>> added to the page cache and/or task page table. This is the reasoning
>> behind the name change.
>
> yeah, definitely less confusing!
>
>> The VM_BUG_ON_PAGE() calls in the *_huge_active() interfaces are not
>> really necessary as we KNOW the page is a hugetlb page. Therefore, they
>> are removed.
>>
>> The routine page_huge_active checked for PageHeadHuge before testing the
>> active bit. This is unnecessary in the case where we hold a reference or
>> lock and know it is a hugetlb head page. page_huge_active is also called
>> without holding a reference or lock (scan_movable_pages), and can race with
>> code freeing the page. The extra check in page_huge_active shortened the
>> race window, but did not prevent the race. Offline code calling
>> scan_movable_pages already deals with these races, so removing the check
>> is acceptable. Add comment to racy code.
>>
>> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
>> Reviewed-by: Oscar Salvador <osalvador@suse.de>
>> Reviewed-by: Muchun Song <songmuchun@bytedance.com>
>> Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
>
> Acked-by: Michal Hocko <mhocko@suse.com>
>
> One nit below
> [...]
>> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
>> index a7eb05315c6e..58be44a915d1 100644
>> --- a/include/linux/hugetlb.h
>> +++ b/include/linux/hugetlb.h
>> @@ -480,9 +480,13 @@ unsigned long hugetlb_get_unmapped_area(struct file *file, unsigned long addr,
>> * HPG_restore_reserve - Set when a hugetlb page consumes a reservation at
>> * allocation time. Cleared when page is fully instantiated. Free
>> * routine checks flag to restore a reservation on error paths.
>> + * HPG_migratable - Set after a newly allocated page is added to the page
>> + * cache and/or page tables. Indicates the page is a candidate for
>> + * migration.
>
> The state change is synchronized by hugetlb_lock.
>
> Pls.
I will update/explain this. But ... hugetlb_lock does not synchronize all
changes of this flag. The flag is set without holding the lock for newly
allocated pages after being added to page cache and/or page tables. This
'signals' the page is a candidate for migration. When the migration code
(isolation, putback, move state) deals with the flag, it does hold the
hugetlb_lock.
This patch did not change any of the synchronization.
--
Mike Kravetz
next prev parent reply other threads:[~2021-01-27 23:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 19:52 [PATCH v3 0/5] create hugetlb flags to consolidate state Mike Kravetz
2021-01-22 19:52 ` [PATCH v3 1/5] hugetlb: use page.private for hugetlb specific page flags Mike Kravetz
2021-01-26 8:17 ` Oscar Salvador
2021-01-27 10:20 ` Michal Hocko
2021-01-27 23:01 ` Mike Kravetz
2021-01-27 10:26 ` Michal Hocko
2021-01-22 19:52 ` [PATCH v3 2/5] hugetlb: convert page_huge_active() HPageMigratable flag Mike Kravetz
2021-01-27 10:25 ` Michal Hocko
2021-01-27 23:27 ` Mike Kravetz [this message]
2021-01-22 19:52 ` [PATCH v3 3/5] hugetlb: only set HPageMigratable for migratable hstates Mike Kravetz
2021-01-26 8:20 ` Oscar Salvador
2021-01-27 10:35 ` Michal Hocko
2021-01-27 23:36 ` Mike Kravetz
2021-01-28 5:52 ` Oscar Salvador
2021-01-28 21:37 ` Andrew Morton
2021-01-28 22:00 ` Mike Kravetz
2021-01-28 22:15 ` Andrew Morton
2021-01-29 9:09 ` Michal Hocko
2021-01-29 18:46 ` Mike Kravetz
2021-02-01 11:49 ` Michal Hocko
2021-02-04 1:11 ` Mike Kravetz
2021-01-22 19:52 ` [PATCH v3 4/5] hugetlb: convert PageHugeTemporary() to HPageTemporary flag Mike Kravetz
2021-01-23 3:15 ` [External] " Muchun Song
2021-01-27 10:39 ` Michal Hocko
2021-01-22 19:52 ` [PATCH v3 5/5] hugetlb: convert PageHugeFreed to HPageFreed flag Mike Kravetz
2021-01-27 10:41 ` Michal Hocko
2021-01-27 23:37 ` Mike Kravetz
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=1d05b4ae-e14d-794e-f2bb-0906cbfc2ba1@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=osalvador@suse.de \
--cc=songmuchun@bytedance.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox