LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, apopple@nvidia.com,
shy828301@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] mm: migrate: Move the page count validation to the proper place
Date: Mon, 16 Aug 2021 18:58:12 +0800 [thread overview]
Message-ID: <6f1b616a-d67c-7580-a3b2-fcb621917063@linux.alibaba.com> (raw)
In-Reply-To: <YRjtquPEpsked951@casper.infradead.org>
On 2021/8/15 18:34, Matthew Wilcox wrote:
> On Sun, Aug 15, 2021 at 02:23:03PM +0800, Baolin Wang wrote:
>> We've got the expected count for anonymous page or file page by
>> expected_page_refs() at the beginning of migrate_page_move_mapping(),
>> thus we should move the page count validation a little forward to
>> reduce duplicated code.
>>
>> Moreover the i_pages lock is not used to guarantee the page refcount
>> safety in migrate_page_move_mapping(), so we can move the getting page
>> count out of the i_pages lock. Since now the migration page has
>> established a migration pte under the page lock now, with the page
>> refcount freezing validation, to ensure that the page references
>> meet the migration requirement.
>
> I remain unconvinced by this.
>
> Looking at folio_migrate_mapping() a little more deeply, I don't
> understand why we first check folio_ref_count() and then attempt
> to free the refcount. Why not just try to freeze it directly?
>
> ie instead of your patch, this:
>
> +++ b/mm/migrate.c
> @@ -403,13 +403,8 @@ int folio_migrate_mapping(struct address_space *mapping,
> newzone = folio_zone(newfolio);
>
> xas_lock_irq(&xas);
> - if (folio_ref_count(folio) != expected_count ||
> - xas_load(&xas) != folio) {
> - xas_unlock_irq(&xas);
> - return -EAGAIN;
> - }
> -
> - if (!folio_ref_freeze(folio, expected_count)) {
> + if (xas_load(&xas) != folio ||
> + !folio_ref_freeze(folio, expected_count)) {
> xas_unlock_irq(&xas);
> return -EAGAIN;
> }
I think this is reasonable, like what we've done in __remove_mapping().
> And since we've got the lock on the page, how can somebody else be
> removing it from the page cache? I think that xas_load() can be
> removed too. So even more simply,
Good point, this is more simply.
>
> +++ b/mm/migrate.c
> @@ -403,12 +403,6 @@ int folio_migrate_mapping(struct address_space *mapping,
> newzone = folio_zone(newfolio);
>
> xas_lock_irq(&xas);
> - if (folio_ref_count(folio) != expected_count ||
> - xas_load(&xas) != folio) {
> - xas_unlock_irq(&xas);
> - return -EAGAIN;
> - }
> -
> if (!folio_ref_freeze(folio, expected_count)) {
> xas_unlock_irq(&xas);
> return -EAGAIN;
>
> but I'm not really set up to test page migration. Does your test suite
> test migrating file-backed pages?
Yes, I've tested above changes, and the mapped file pages migration
works well. So can I resend this patch set with your Suggested-by tag?
Thanks.
next prev parent reply other threads:[~2021-08-16 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 6:23 [PATCH v2 0/4] Some cleanup for page migration Baolin Wang
2021-08-15 6:23 ` [PATCH v2 1/4] mm: migrate: Move the page count validation to the proper place Baolin Wang
2021-08-15 10:34 ` Matthew Wilcox
2021-08-16 10:58 ` Baolin Wang [this message]
2021-08-15 6:23 ` [PATCH v2 2/4] mm: migrate: Introduce a local variable to get the number of pages Baolin Wang
2021-08-15 6:23 ` [PATCH v2 3/4] mm: migrate: Fix the incorrect function name in comments Baolin Wang
2021-08-15 6:23 ` [PATCH v2 4/4] mm: migrate: Change to use bool type for 'page_was_mapped' Baolin 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=6f1b616a-d67c-7580-a3b2-fcb621917063@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=willy@infradead.org \
--subject='Re: [PATCH v2 1/4] mm: migrate: Move the page count validation to the proper place' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).