summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorViacheslav Dubeyko <slava@dubeyko.com>2026-07-24 15:27:44 -0700
committerChristian Brauner <brauner@kernel.org>2026-07-27 11:43:15 +0200
commite7b2c51c3fedd68bf97d9a49cfbe76b240aee41d (patch)
tree0699ad338fc8ff5ff5ad0b7e59d7988e3e72026a /scripts/Makefile.thinlto
parent1590cf0329716306e948a8fc29f1d3ee87d3989f (diff)
downloadlinux-next-e7b2c51c3fedd68bf97d9a49cfbe76b240aee41d.tar.gz
linux-next-e7b2c51c3fedd68bf97d9a49cfbe76b240aee41d.zip
nilfs2: add iomap operations for direct I/O reads
Add iomap.c and iomap.h with a read-only nilfs_iomap_ops, wrapping the existing nilfs_bmap_lookup_contig() lookup to report a mapped range, a real hole, or an EOF-clamped range to iomap core. NILFS2 is a log-structured, copy-on-write filesystem: newly allocated blocks are only given a real disk address when the segment constructor writes them out as part of a log, which walks buffer_head lists directly and is not integrated with the generic address_space writeback path. Because of that, only the read-only side of the mapping is added - buffered writes, writeback, and mmap's ->page_mkwrite() will stay on the existing buffer_head based path (nilfs_get_block(), nilfs_write_begin/end(), nilfs_writepages(), nilfs_dirty_folio(), block_page_mkwrite()). Signed-off-by: Viacheslav Dubeyko <slava@dubeyko.com> Link: https://patch.msgid.link/20260724222745.2107464-2-slava@dubeyko.com Acked-by: Ryusuke Konishi <konishi.ryusuke@gmail.com> cc: Christoph Hellwig <hch@lst.de> cc: Ryusuke Konishi <konishi.ryusuke@gmail.com> cc: linux-nilfs@vger.kernel.org cc: linux-fsdevel@vger.kernel.org Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions