Message ID | 20201021062554.68132-1-wqu@suse.com (mailing list archive) |
---|---|
Headers | show |
Series | btrfs: add basic rw support for subpage sector size | expand |
On Wed, Oct 21, 2020 at 02:24:46PM +0800, Qu Wenruo wrote: > === Patchset structure === > Patch 01~03: Small bug fixes > Patch 04~22: Generic cleanup and refactors, which make sense without > subpage support > Patch 23~27: Subpage specific cleanup and refactors. > Patch 28~42: Enablement for subpage RO mount > Patch 43~52: Enablement for subpage metadata write > Patch 53~68: Enablement for subpage data write (although still in > page size) That's a sane grouping to merge it from the top, though it still could be some updates required. There are some pending patchsets for next and I don't have an estimate for conflicts regarding the cleanups you have in this patchset so we'll see. All up to 27 should be mergeable in this dev cycle.
On 2020/10/21 下午7:22, David Sterba wrote: > On Wed, Oct 21, 2020 at 02:24:46PM +0800, Qu Wenruo wrote: >> === Patchset structure === >> Patch 01~03: Small bug fixes >> Patch 04~22: Generic cleanup and refactors, which make sense without >> subpage support >> Patch 23~27: Subpage specific cleanup and refactors. >> Patch 28~42: Enablement for subpage RO mount >> Patch 43~52: Enablement for subpage metadata write >> Patch 53~68: Enablement for subpage data write (although still in >> page size) > > That's a sane grouping to merge it from the top, though it still could > be some updates required. There are some pending patchsets for next and > I don't have an estimate for conflicts regarding the cleanups you have > in this patchset so we'll see. All up to 27 should be mergeable in this > dev cycle. > That's great, if the conflicts are not manageable, feel free to ask me to do the rebase. The main conflicts I can guess is from the metadata readpage refactor from Nik, but my current structure is already using a similar way to call submit_extent_page() directly, so I guess it shouldn't be too destructive. Thanks, Qu
On Wed, Oct 21, 2020 at 02:24:46PM +0800, Qu Wenruo wrote: > Patches can be fetched from github: > https://github.com/adam900710/linux/tree/subpage_data_fullpage_write > > Qu Wenruo (67): So far I've merged btrfs: extent_io: fix the comment on lock_extent_buffer_for_io() btrfs: extent_io: update the comment for find_first_extent_bit() btrfs: extent_io: sink the failed_start parameter to set_extent_bit() btrfs: disk-io: replace fs_info and private_data with inode for btrfs_wq_submit_bio() btrfs: inode: sink parameter start and len to check_data_csum() btrfs: extent_io: rename pages_locked in process_pages_contig() btrfs: extent_io: only require sector size alignment for page read btrfs: extent_io: rename page_size to io_size in submit_extent_page() to misc-next. This is from the first 20, the easy and safe changes. There are few more that need more explanation or another look.
On 2020/11/2 下午10:56, David Sterba wrote: > On Wed, Oct 21, 2020 at 02:24:46PM +0800, Qu Wenruo wrote: >> Patches can be fetched from github: >> https://github.com/adam900710/linux/tree/subpage_data_fullpage_write >> >> Qu Wenruo (67): > > So far I've merged > > btrfs: extent_io: fix the comment on lock_extent_buffer_for_io() > btrfs: extent_io: update the comment for find_first_extent_bit() > btrfs: extent_io: sink the failed_start parameter to set_extent_bit() > btrfs: disk-io: replace fs_info and private_data with inode for btrfs_wq_submit_bio() > btrfs: inode: sink parameter start and len to check_data_csum() > btrfs: extent_io: rename pages_locked in process_pages_contig() > btrfs: extent_io: only require sector size alignment for page read > btrfs: extent_io: rename page_size to io_size in submit_extent_page() > > to misc-next. This is from the first 20, the easy and safe changes. > There are few more that need more explanation or another look. > That's great. BTW, for next update, I should rebase all patches to current misc-next right? Especially to take advantage of things like sectorsize_bits. BTW, for next round patches, should I send all the patches in a huge batch, or just send the safe refactors (with comments addresses)? THanks, Qu