Re: [PATCH 31/41] fs: Provide functions for handling mapping_metadata_bhs directly
Jan Kara <[email protected]> Wed, 25 Mar 2026 20:00:42 +0100
| Newsgroups | gmane.linux.kernel.aio.general,gmane.linux.file-systems,gmane.linux.block,gmane.comp.file-systems.ext4,gmane.linux.kernel.mm |
|---|---|
| Message-ID | <f7e57f3wfmzkh7wcsq662q5igqnxza4ryfk4uzm5kba5f5stfg@be4tpgtp5nga> |
On Mon 23-03-26 22:51:24, Christoph Hellwig wrote: > On Fri, Mar 20, 2026 at 02:41:26PM +0100, Jan Kara wrote: > > As part of transition toward moving mapping_metadata_bhs to fs-private > > part of the inode, provide functions for operations on this list > > directly instead of going through the inode / mapping. > > > > Signed-off-by: Jan Kara <[email protected]> ... > > @@ -553,9 +547,8 @@ EXPORT_SYMBOL_GPL(mmb_has_buffers); > > * buffer stays on our list until IO completes (at which point it can be > > * reaped). > > */ > > -int sync_mapping_buffers(struct address_space *mapping) > > +int mmb_sync_buffers(struct mapping_metadata_bhs *mmb) > > mmb and buffers in the same name feels a bit redundant. > > mmc_sync_all? mapping_sync_buffers? I've called this just mmb_sync() and I've also shortened mmb_invalidate_buffers() to mmb_invalidate(). > > > +int generic_mmb_fsync_noflush(struct file *file, > > + struct mapping_metadata_bhs *mmb, > > + loff_t start, loff_t end, bool datasync) > > mmb_fsync? mapping_buffers_fsync? This I've called mmb_fsync(). Honza -- Jan Kara <[email protected]> SUSE Labs, CR -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to [email protected]. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: <a href=mailto:"[email protected]">[email protected]</a>