From: Christian Brauner <brauner@kernel.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 00/11] Remove aops->writepage
Date: Fri, 28 Mar 2025 10:40:23 +0100 [thread overview]
Message-ID: <20250328-farbschichten-begossen-0190490de275@brauner> (raw)
In-Reply-To: <20250307135414.2987755-1-willy@infradead.org>
On Fri, Mar 07, 2025 at 01:54:00PM +0000, Matthew Wilcox wrote:
> I was preparing for LSFMM and noticed that actually we're almost done
> with the writepage conversion. This patchset finishes it off.
> Something changed in my test environment and now it crashes before
> even starting a run, so this is only build tested.
>
> The first five patches (f2fs and vboxsf) are uninteresting. I'll try
> and get those into linux-next for the imminent merge window. I think
> the migrate and writeback patches are good, but maybe I've missed
> something. Then we come to i915 needing to tell shmem to do writeout,
> so I added a module-accessible function to do that. I also removed
> the setting/clearing of reclaim, which would be easy to bring back if
> it's really needed. Patch 10 is probably the exciting one where
> pageout() calls swap or shmem directly. And then patch 11 really just
> removes the op itself and the documentation for it. I may have
> over-trimmed here, but some of the documentation was so out of date it
> was hard to tell what was worth preserving.
>
> Anyway, let's see what the bots make of this. This is against
> next-20250307.
Once you're ready it would be nice if you could resend this based on
mainline (can be today) and then I'll pick it up.
Christian
prev parent reply other threads:[~2025-03-28 9:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 13:54 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
2025-04-01 16:26 ` Matthew Wilcox
2025-05-02 14:33 ` Thomas Hellström
2025-03-28 9:40 ` Christian Brauner [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=20250328-farbschichten-begossen-0190490de275@brauner \
--to=brauner@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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