From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <jgowans@amazon.com>,
<yuzhao@google.com>
Subject: Re: [PATCH -next 1/2] mm: compaction: convert to use a folio in isolate_migratepages_block()
Date: Wed, 14 Jun 2023 19:21:02 +0800 [thread overview]
Message-ID: <6acaf695-1c77-c0c6-a1d4-4cc946310997@huawei.com> (raw)
In-Reply-To: <99dabd49-16c7-2858-e502-1bb390e13859@huawei.com>
On 2023/6/13 9:53, Kefeng Wang wrote:
>
>
> On 2023/6/12 22:41, Matthew Wilcox wrote:
>> On Mon, Jun 12, 2023 at 10:34:13PM +0800, Kefeng Wang wrote:
>>> @@ -959,7 +960,8 @@ isolate_migratepages_block(struct compact_control
>>> *cc, unsigned long low_pfn,
>>> * Hugepage was successfully isolated and placed
>>> * on the cc->migratepages list.
>>> */
>>> - low_pfn += compound_nr(page) - 1;
>>> + folio = page_folio(page);
>>> + low_pfn += folio_nr_pages(folio) - 1;
>>> goto isolate_success_no_list;
>>
>> Why is this safe? That is, how do we know that the folio can't be
>> dissolved under us at this point, then reallocated and hit the
>> VM_BUG_ON_PGFLAGS(PageTail(page), page) in folio_flags() when we
>> test folio_test_large()?
>
> This is successfully isolated path, after isolate_hugetlb(), the folio
> reference is incremented, so I think the folio can't be dissolved here,
> correct me if I am wrong.
Hi Matthew,is it enough for the above conversion from page to folio with
reference?
prev parent reply other threads:[~2023-06-14 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 14:34 Kefeng Wang
2023-06-12 14:34 ` [PATCH -next 2/2] mm: kill [add|del]_page_to_lru_list() Kefeng Wang
2023-06-12 19:10 ` Yu Zhao
2023-06-12 14:41 ` [PATCH -next 1/2] mm: compaction: convert to use a folio in isolate_migratepages_block() Matthew Wilcox
2023-06-13 1:53 ` Kefeng Wang
2023-06-14 11:21 ` Kefeng Wang [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=6acaf695-1c77-c0c6-a1d4-4cc946310997@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=jgowans@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
--cc=yuzhao@google.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