From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-aio@kvack.org, linux-nfs@vger.kernel.org,
cluster-devel@redhat.com, linux-ntfs-dev@lists.sourceforge.net,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, linux-mm@kvack.org,
linux-mtd@lists.infradead.org, ocfs2-devel@oss.oracle.com,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-xfs@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2 03/19] fs: Add aops->migrate_folio
Date: Fri, 10 Jun 2022 12:17:33 +0200 [thread overview]
Message-ID: <e287a12d-29d9-da69-9315-52414341cbd1@redhat.com> (raw)
In-Reply-To: <YqIFHPJZNMrmtXlh@casper.infradead.org>
On 09.06.22 16:35, Matthew Wilcox wrote:
> On Thu, Jun 09, 2022 at 02:50:20PM +0200, David Hildenbrand wrote:
>> On 08.06.22 17:02, Matthew Wilcox (Oracle) wrote:
>>> diff --git a/Documentation/filesystems/locking.rst b/Documentation/filesystems/locking.rst
>>> index c0fe711f14d3..3d28b23676bd 100644
>>> --- a/Documentation/filesystems/locking.rst
>>> +++ b/Documentation/filesystems/locking.rst
>>> @@ -253,7 +253,8 @@ prototypes::
>>> void (*free_folio)(struct folio *);
>>> int (*direct_IO)(struct kiocb *, struct iov_iter *iter);
>>> bool (*isolate_page) (struct page *, isolate_mode_t);
>>> - int (*migratepage)(struct address_space *, struct page *, struct page *);
>>> + int (*migrate_folio)(struct address_space *, struct folio *dst,
>>> + struct folio *src, enum migrate_mode);
>>> void (*putback_page) (struct page *);
>>
>> isolate_page/putback_page are leftovers from the previous patch, no?
>
> Argh, right, I completely forgot I needed to update the documentation in
> that patch.
>
>>> +++ b/Documentation/vm/page_migration.rst
>>> @@ -181,22 +181,23 @@ which are function pointers of struct address_space_operations.
>>> Once page is successfully isolated, VM uses page.lru fields so driver
>>> shouldn't expect to preserve values in those fields.
>>>
>>> -2. ``int (*migratepage) (struct address_space *mapping,``
>>> -| ``struct page *newpage, struct page *oldpage, enum migrate_mode);``
>>> -
>>> - After isolation, VM calls migratepage() of driver with the isolated page.
>>> - The function of migratepage() is to move the contents of the old page to the
>>> - new page
>>> - and set up fields of struct page newpage. Keep in mind that you should
>>> - indicate to the VM the oldpage is no longer movable via __ClearPageMovable()
>>> - under page_lock if you migrated the oldpage successfully and returned
>>> - MIGRATEPAGE_SUCCESS. If driver cannot migrate the page at the moment, driver
>>> - can return -EAGAIN. On -EAGAIN, VM will retry page migration in a short time
>>> - because VM interprets -EAGAIN as "temporary migration failure". On returning
>>> - any error except -EAGAIN, VM will give up the page migration without
>>> - retrying.
>>> -
>>> - Driver shouldn't touch the page.lru field while in the migratepage() function.
>>> +2. ``int (*migrate_folio) (struct address_space *mapping,``
>>> +| ``struct folio *dst, struct folio *src, enum migrate_mode);``
>>> +
>>> + After isolation, VM calls the driver's migrate_folio() with the
>>> + isolated folio. The purpose of migrate_folio() is to move the contents
>>> + of the source folio to the destination folio and set up the fields
>>> + of destination folio. Keep in mind that you should indicate to the
>>> + VM the source folio is no longer movable via __ClearPageMovable()
>>> + under folio if you migrated the source successfully and returned
>>> + MIGRATEPAGE_SUCCESS. If driver cannot migrate the folio at the
>>> + moment, driver can return -EAGAIN. On -EAGAIN, VM will retry folio
>>> + migration in a short time because VM interprets -EAGAIN as "temporary
>>> + migration failure". On returning any error except -EAGAIN, VM will
>>> + give up the folio migration without retrying.
>>> +
>>> + Driver shouldn't touch the folio.lru field while in the migrate_folio()
>>> + function.
>>>
>>> 3. ``void (*putback_page)(struct page *);``
>>
>> Hmm, here it's a bit more complicated now, because we essentially have
>> two paths: LRU+migrate_folio or !LRU+movable_ops
>> (isolate/migrate/putback page)
>
> Oh ... actually, this is just documenting the driver side of things.
> I don't really like how it's written. Here, have some rewritten
> documentation (which is now part of the previous patch):
>
LGTM, thanks.
--
Thanks,
David / dhildenb
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-06-10 10:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:02 [f2fs-dev] [PATCH v2 00/19] Convert aops->migratepage to aops->migrate_folio Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 01/19] secretmem: Remove isolate_page Matthew Wilcox (Oracle)
2022-06-09 12:46 ` David Hildenbrand
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 02/19] mm: Convert all PageMovable users to movable_operations Matthew Wilcox (Oracle)
2022-06-09 10:23 ` David Hildenbrand
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 03/19] fs: Add aops->migrate_folio Matthew Wilcox (Oracle)
2022-06-09 12:50 ` David Hildenbrand
2022-06-09 14:35 ` Matthew Wilcox
2022-06-10 10:17 ` David Hildenbrand [this message]
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 04/19] mm/migrate: Convert fallback_migrate_page() to fallback_migrate_folio() Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 05/19] mm/migrate: Convert writeout() to take a folio Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 06/19] mm/migrate: Convert buffer_migrate_page() to buffer_migrate_folio() Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 07/19] mm/migrate: Convert expected_page_refs() to folio_expected_refs() Matthew Wilcox (Oracle)
2022-07-08 2:50 ` Hugh Dickins via Linux-f2fs-devel
2022-07-08 3:29 ` Matthew Wilcox
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 08/19] btrfs: Convert btree_migratepage to migrate_folio Matthew Wilcox (Oracle)
2022-06-09 16:25 ` David Sterba
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 09/19] nfs: Convert " Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 10/19] mm/migrate: Convert migrate_page() to migrate_folio() Matthew Wilcox (Oracle)
2022-06-09 16:26 ` David Sterba
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 11/19] mm/migrate: Add filemap_migrate_folio() Matthew Wilcox (Oracle)
2022-06-08 15:22 ` Darrick J. Wong
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 12/19] btrfs: Convert btrfs_migratepage to migrate_folio Matthew Wilcox (Oracle)
2022-06-09 16:33 ` David Sterba
2022-06-09 17:40 ` Matthew Wilcox
2022-06-09 23:05 ` David Sterba
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 13/19] ubifs: Convert to filemap_migrate_folio() Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 14/19] f2fs: " Matthew Wilcox (Oracle)
2022-06-15 8:11 ` Chao Yu
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 15/19] aio: Convert to migrate_folio Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 16/19] hugetlb: " Matthew Wilcox (Oracle)
2022-06-09 3:53 ` Muchun Song
2022-06-09 20:51 ` Mike Kravetz
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 17/19] secretmem: " Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 18/19] fs: Remove aops->migratepage() Matthew Wilcox (Oracle)
2022-06-08 15:02 ` [f2fs-dev] [PATCH v2 19/19] mm/folio-compat: Remove migration compatibility functions Matthew Wilcox (Oracle)
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=e287a12d-29d9-da69-9315-52414341cbd1@redhat.com \
--to=david@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-aio@kvack.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=linux-xfs@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).