From: "陈涛涛 Taotao Chen" <chentaotao@didiglobal.com>
To: "tytso@mit.edu" <tytso@mit.edu>,
"hch@infradead.org" <hch@infradead.org>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"willy@infradead.org" <willy@infradead.org>,
"brauner@kernel.org" <brauner@kernel.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"rodrigo.vivi@intel.com" <rodrigo.vivi@intel.com>,
"tursulin@ursulin.net" <tursulin@ursulin.net>,
"airlied@gmail.com" <airlied@gmail.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chentao325@qq.com" <chentao325@qq.com>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"陈涛涛 Taotao Chen" <chentaotao@didiglobal.com>
Subject: [PATCH v5 0/5] fs: refactor write_begin/write_end and add ext4 IOCB_DONTCACHE support
Date: Thu, 10 Jul 2025 10:14:06 +0000 [thread overview]
Message-ID: <20250710101404.362146-1-chentaotao@didiglobal.com> (raw)
From: Taotao Chen <chentaotao@didiglobal.com>
This patch series refactors the address_space_operations write_begin()
and write_end() callbacks to take const struct kiocb * as their first
argument, allowing IOCB flags such as IOCB_DONTCACHE to propagate to the
filesystem's buffered I/O path.
Ext4 is updated to implement handling of the IOCB_DONTCACHE flag and
advertises support via the FOP_DONTCACHE file operation flag.
Additionally, the i915 driver's shmem write paths are updated to bypass
the legacy write_begin/write_end interface in favor of directly
calling write_iter() with a constructed synchronous kiocb. Another i915
change replaces a manual write loop with kernel_write() during GEM shmem
object creation.
Tested with ext4 and i915 GEM workloads.
This patch series is based on the vfs-6.17.misc branch.
Changes since v4:
- Updated write_begin_get_folio() comment and made it static inline in header.
Taotao Chen (5):
drm/i915: Use kernel_write() in shmem object create
drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter
fs: change write_begin/write_end interface to take struct kiocb *
mm/pagemap: add write_begin_get_folio() helper function
ext4: support uncached buffered I/O
Documentation/filesystems/locking.rst | 4 +-
Documentation/filesystems/vfs.rst | 6 +-
block/fops.c | 13 ++-
drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 114 ++++++----------------
fs/adfs/inode.c | 9 +-
fs/affs/file.c | 26 ++---
fs/bcachefs/fs-io-buffered.c | 4 +-
fs/bcachefs/fs-io-buffered.h | 4 +-
fs/bfs/file.c | 7 +-
fs/buffer.c | 26 ++---
fs/ceph/addr.c | 10 +-
fs/ecryptfs/mmap.c | 10 +-
fs/exfat/file.c | 11 +--
fs/exfat/inode.c | 16 +--
fs/ext2/inode.c | 11 ++-
fs/ext4/file.c | 3 +-
fs/ext4/inode.c | 30 +++---
fs/f2fs/data.c | 8 +-
fs/fat/inode.c | 18 ++--
fs/fuse/file.c | 14 ++-
fs/hfs/hfs_fs.h | 2 +-
fs/hfs/inode.c | 4 +-
fs/hfsplus/hfsplus_fs.h | 6 +-
fs/hfsplus/inode.c | 8 +-
fs/hostfs/hostfs_kern.c | 8 +-
fs/hpfs/file.c | 18 ++--
fs/hugetlbfs/inode.c | 9 +-
fs/jffs2/file.c | 28 +++---
fs/jfs/inode.c | 16 +--
fs/libfs.c | 11 ++-
fs/minix/inode.c | 7 +-
fs/nfs/file.c | 8 +-
fs/nilfs2/inode.c | 8 +-
fs/ntfs3/file.c | 4 +-
fs/ntfs3/inode.c | 7 +-
fs/ntfs3/ntfs_fs.h | 10 +-
fs/ocfs2/aops.c | 6 +-
fs/omfs/file.c | 7 +-
fs/orangefs/inode.c | 16 +--
fs/ubifs/file.c | 5 +-
fs/udf/inode.c | 11 ++-
fs/ufs/inode.c | 16 +--
fs/vboxsf/file.c | 5 +-
include/linux/buffer_head.h | 4 +-
include/linux/fs.h | 11 ++-
include/linux/pagemap.h | 27 +++++
mm/filemap.c | 4 +-
mm/shmem.c | 12 +--
48 files changed, 327 insertions(+), 295 deletions(-)
--
2.34.1
next reply other threads:[~2025-07-10 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 10:14 陈涛涛 Taotao Chen [this message]
2025-07-10 10:14 ` [PATCH v5 1/5] drm/i915: Use kernel_write() in shmem object create 陈涛涛 Taotao Chen
2025-07-10 10:14 ` [PATCH v5 2/5] drm/i915: Refactor shmem_pwrite() to use kiocb and write_iter 陈涛涛 Taotao Chen
2025-07-10 10:14 ` [PATCH v5 3/5] fs: change write_begin/write_end interface to take struct kiocb * 陈涛涛 Taotao Chen
2025-07-10 10:14 ` [PATCH v5 4/5] mm/pagemap: add write_begin_get_folio() helper function 陈涛涛 Taotao Chen
2025-07-10 10:14 ` [PATCH v5 5/5] ext4: support uncached buffered I/O 陈涛涛 Taotao Chen
2025-07-14 9:11 ` [PATCH v5 0/5] fs: refactor write_begin/write_end and add ext4 IOCB_DONTCACHE support Christian Brauner
2025-07-16 3:23 ` Taotao Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250710101404.362146-1-chentaotao@didiglobal.com \
--to=chentaotao@didiglobal.com \
--cc=adilger.kernel@dilger.ca \
--cc=airlied@gmail.com \
--cc=brauner@kernel.org \
--cc=chentao325@qq.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.li@vivo.com \
--cc=hch@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox