From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Wilcox <willy@infradead.org>, Fan Ni <nifan.cxl@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 11/11] fs: Remove aops->writepage
Date: Tue, 18 Mar 2025 09:10:38 +0100 [thread overview]
Message-ID: <9937a6346feccb7ab739aff63a084f63f3ad4382.camel@linux.intel.com> (raw)
In-Reply-To: <Z9iibbHs-jHTu7LP@casper.infradead.org>
On Mon, 2025-03-17 at 22:30 +0000, Matthew Wilcox wrote:
> On Mon, Mar 17, 2025 at 03:22:30AM +0000, Matthew Wilcox wrote:
> > On Sun, Mar 16, 2025 at 06:08:52PM -0700, Fan Ni wrote:
> > > On Fri, Mar 07, 2025 at 01:54:11PM +0000, Matthew Wilcox (Oracle)
> > > wrote:
> > > > All callers and implementations are now removed, so remove the
> > > > operation
> > > > and update the documentation to match.
> > > >
> > > > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> > > > ---
> > >
> > > Hi Matthew,
> > >
> > > Tried to apply the remaining patches in the patchest (Patch 5-
> > > 11) which
> > > have not picked up by linux-next. It seems we have more to
> > > cleanup.
> > >
> > > For example, I hit the following issue when try to compile
> > > ----------------------------------------------------------------
> > > drivers/gpu/drm/ttm/ttm_backup.c: In function
> > > ‘ttm_backup_backup_page’:
> > > drivers/gpu/drm/ttm/ttm_backup.c:139:39: error: ‘const struct
> > > address_space_operations’ has no member named ‘writepage’; did
> > > you mean ‘writepages’?
> > > 139 | ret = mapping->a_ops-
> > > >writepage(folio_file_page(to_folio, idx), &wbc);
> >
> > Looks like that was added to linux-next after I completed the
> > removal of
> > ->writepage. Thomas, what's going on here?
>
> This patch fixes the compilation problem. But I don't understand why
> it's messing with the reclaim flag. Thomas, can you explain?
Hi, Sorry for not responding earlier. The patch that uses writepage()
here has been around for quite some time waiting for reviews / acks so
I failed to notice that it's going away.
Anyway the reclaim flag clearing follows that of pageout() in vmscan.c
which was also the case for the i915_gem_shmem.c usage in
__shmem_writeback(). My understanding was that if the writeback was
already completed at that point, the reclaim flag was no longer
desirable.
Let me know if this requires some action on my side. Unfortunately
freedesktop.org is down for maintainance, possibly for the whole week,
so there will be no drm subsystem PRs this week AFAICT.
The fix below looks good to me, BTW.
Thanks,
Thomas
>
> +++ b/drivers/gpu/drm/ttm/ttm_backup.c
> @@ -136,13 +136,13 @@ ttm_backup_backup_page(struct ttm_backup
> *backup, struct page *page,
> .for_reclaim = 1,
> };
> folio_set_reclaim(to_folio);
> - ret = mapping->a_ops-
> >writepage(folio_file_page(to_folio, idx), &wbc);
> + ret = shmem_writeout(to_folio, &wbc);
> if (!folio_test_writeback(to_folio))
> folio_clear_reclaim(to_folio);
> /*
> - * If writepage succeeds, it unlocks the folio.
> - * writepage() errors are otherwise dropped, since
> writepage()
> - * is only best effort here.
> + * If writeout succeeds, it unlocks the folio.
> errors
> + * are otherwise dropped, since writeout is only best
> + * effort here.
> */
> if (ret)
> folio_unlock(to_folio);
>
next prev parent reply other threads:[~2025-03-18 8:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 13:54 [PATCH 00/11] " Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 01/11] f2fs: Remove check for ->writepage Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 02/11] f2fs: Remove f2fs_write_data_page() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 03/11] f2fs: Remove f2fs_write_meta_page() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 04/11] f2fs: Remove f2fs_write_node_page() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 05/11] vboxsf: Convert to writepages Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 06/11] migrate: Remove call to ->writepage Matthew Wilcox (Oracle)
2025-03-27 15:04 ` Zi Yan
2025-03-27 16:52 ` Matthew Wilcox
2025-03-27 17:22 ` Zi Yan
2025-04-01 13:32 ` David Hildenbrand
2025-03-07 13:54 ` [PATCH 07/11] writeback: Remove writeback_use_writepage() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 08/11] shmem: Add shmem_writeout() Matthew Wilcox (Oracle)
2025-03-08 5:31 ` Baolin Wang
2025-03-07 13:54 ` [PATCH 09/11] i915: Use writeback_iter() Matthew Wilcox (Oracle)
2025-03-07 13:54 ` [PATCH 10/11] mm: Remove swap_writepage() and shmem_writepage() Matthew Wilcox (Oracle)
2025-03-08 5:34 ` Baolin Wang
2025-03-07 13:54 ` [PATCH 11/11] fs: Remove aops->writepage Matthew Wilcox (Oracle)
2025-03-17 1:08 ` Fan Ni
2025-03-17 3:22 ` Matthew Wilcox
2025-03-17 22:30 ` Matthew Wilcox
2025-03-18 8:10 ` Thomas Hellström [this message]
2025-04-01 16:26 ` Matthew Wilcox
2025-05-02 14:33 ` Thomas Hellström
2025-03-28 9:40 ` [PATCH 00/11] " Christian Brauner
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=9937a6346feccb7ab739aff63a084f63f3ad4382.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nifan.cxl@gmail.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