On Tue, Apr 06, 2021 at 10:31:58AM +0800, Anand Jain wrote: > On 05/04/2021 14:14, Qu Wenruo wrote: > > > > > > On 2021/4/3 下午7:08, David Sterba wrote: > >> On Thu, Mar 25, 2021 at 03:14:32PM +0800, Qu Wenruo wrote: > >>> This patchset can be fetched from the following github repo, along with > >>> the full subpage RW support: > >>> https://github.com/adam900710/linux/tree/subpage > >>> > >>> This patchset is for metadata read write support. > >> > >>> Qu Wenruo (13): > >>> btrfs: add sysfs interface for supported sectorsize > >>> btrfs: use min() to replace open-code in btrfs_invalidatepage() > >>> btrfs: remove unnecessary variable shadowing in > >>> btrfs_invalidatepage() > >>> btrfs: refactor how we iterate ordered extent in > >>> btrfs_invalidatepage() > >>> btrfs: introduce helpers for subpage dirty status > >>> btrfs: introduce helpers for subpage writeback status > >>> btrfs: allow btree_set_page_dirty() to do more sanity check on > >>> subpage > >>> metadata > >>> btrfs: support subpage metadata csum calculation at write time > >>> btrfs: make alloc_extent_buffer() check subpage dirty bitmap > >>> btrfs: make the page uptodate assert to be subpage compatible > >>> btrfs: make set/clear_extent_buffer_dirty() to be subpage compatible > >>> btrfs: make set_btree_ioerr() accept extent buffer and to be subpage > >>> compatible > >>> btrfs: add subpage overview comments > >> > >> Moved from topic branch to misc-next. > >> > > > > Note sure if it's too late, but I inserted the last comment patch into > > the wrong location. > > > > In fact, there are 4 more patches to make > > > > subpage metadata RW really work: > > I took some time to go through these patches, which are lined up for > integration. > > With this set of patches that are being integrated, we don't yet > support RW mount of filesystem if PAGESIZE > sectorsize as a whole. > Subpage metadata RW support, how is it to be used in the production? > OR How is this supposed to be tested?
What gets merged to misc-next is incrementally adding support for the whole subpage feature. This would quite hard to get in in one go so it's been split to patchsets with known limitations. Qu lists what works and what does not in the cover letter. With known missing functionality it obviously can't be used for production, just for testing. There are likely patches in Qu's development branches and more patches still to be written, so even the testing is partial with known failures or bugs. > OR should you just cleanup the title as preparatory patches to support > subpage RW? It is confusing. I think the title says what the patchset does, adding rw support for metadata, in a sense it's still preparatory, yes.
