From: Namjae Jeon <linkinjeon@kernel.org>
To: brauner@kernel.org, djwong@kernel.org, hyc.lee@gmail.com
Cc: willy@infradead.org, xiang@kernel.org, hch@lst.de,
linux-fsdevel@vger.kernel.org,
Namjae Jeon <linkinjeon@kernel.org>
Subject: [PATCH 0/2] iomap/ntfs: remove over-strict inline data check and optimize ntfs
Date: Fri, 24 Apr 2026 06:32:01 +0900 [thread overview]
Message-ID: <20260423213203.5533-1-linkinjeon@kernel.org> (raw)
This patch series aims to remove an unnecessarily strict boundary
check for IOMAP_INLINE data and, as a result, optimize the NTFS
driver's handling of resident attributes. The first patch removes
iomap_inline_data_valid() and its callers in the iomap core.
Currently, this check prevents inline_data from crossing a PAGE_SIZE
boundary. If the filesystem provides a valid mapping, iomap should trust
it regardless of page boundaries.
The second patch updates the NTFS driver to take advantage of this
change. Previously, NTFS performed redundant page allocations and
memcpy operations to ensure page-aligned inline data. By removing
these steps, we simplify the NTFS iomap implementation and improve
performance for resident file I/O.
Namjae Jeon (2):
iomap: remove over-strict inline data boundary check
ntfs: use direct pointer for inline data to avoid redundant allocation
fs/iomap/buffered-io.c | 1 -
fs/iomap/direct-io.c | 3 --
fs/ntfs/iomap.c | 76 ++++--------------------------------------
include/linux/iomap.h | 10 ------
4 files changed, 6 insertions(+), 84 deletions(-)
--
2.25.1
next reply other threads:[~2026-04-23 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 21:32 Namjae Jeon [this message]
2026-04-23 21:32 ` [PATCH 1/2] iomap: remove over-strict inline data boundary check Namjae Jeon
2026-04-24 13:30 ` Christoph Hellwig
2026-04-24 15:06 ` Gao Xiang
2026-04-23 21:32 ` [PATCH 2/2] ntfs: use direct pointer for inline data to avoid redundant allocation Namjae Jeon
2026-04-24 13:30 ` Christoph Hellwig
2026-04-25 18:37 ` DaeMyung Kang
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=20260423213203.5533-1-linkinjeon@kernel.org \
--to=linkinjeon@kernel.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=hyc.lee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.org \
--cc=xiang@kernel.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