[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y2Vw2UBkti7MeG5U@casper.infradead.org>
Date: Fri, 4 Nov 2022 20:06:49 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Dave Chinner <david@...morbit.com>
Cc: Vishal Moola <vishal.moola@...il.com>,
linux-fsdevel@...r.kernel.org, linux-afs@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org,
ceph-devel@...r.kernel.org, linux-cifs@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
cluster-devel@...hat.com, linux-nilfs@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH 04/23] page-writeback: Convert write_cache_pages() to use
filemap_get_folios_tag()
On Fri, Nov 04, 2022 at 11:32:35AM +1100, Dave Chinner wrote:
> At minimum, it needs to be documented, though I'd much prefer that
> we explicitly duplicate write_cache_pages() as write_cache_folios()
> with a callback that takes a folio and change the code to be fully
> multi-page folio safe. Then filesystems that support folios (and
> large folios) natively can be passed folios without going through
> this crappy "folio->page, page->folio" dance because the writepage
> APIs are unaware of multi-page folio constructs.
There are a lot of places which go through the folio->page->folio
dance, and this one wasn't even close to the top of my list. That
said, it has a fairly small number of callers -- ext4, fuse, iomap,
mpage, nfs, orangefs. So Vishal, this seems like a good project for you
to take on next -- convert write_cache_pages() to write_cache_folios()
and writepage_t to write_folio_t.
Powered by blists - more mailing lists