From: Daniel Lee <chullee@google.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Daniel Lee <chullee@google.com>
Subject: [PATCH 0/2] f2fs: Fix DIO flags and add ioprio hint
Date: Wed, 11 Jun 2025 16:37:04 -0700 [thread overview]
Message-ID: <20250611233706.572784-1-chullee@google.com> (raw)
The first patch corrects an issue where Direct I/O (DIO) writes ignore
bio flag hints (e.g., F2FS_IOPRIO_WRITE for REQ_PRIO),
making them inconsistent with buffered I/O.
The second patch is to set an I/O priority hint for hot files on creation
and pinned files by default.
Daniel Lee (2):
f2fs: Apply bio flags to direct I/O
f2fs: use ioprio hint for hot and pinned files
fs/f2fs/data.c | 8 ++++----
fs/f2fs/f2fs.h | 23 +++++++++++++++++++++++
fs/f2fs/file.c | 15 +++++++++++++++
fs/f2fs/namei.c | 11 +++++++----
4 files changed, 49 insertions(+), 8 deletions(-)
--
2.50.0.rc1.591.g9c95f17f64-goog
next reply other threads:[~2025-06-11 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 23:37 Daniel Lee [this message]
2025-06-11 23:37 ` [PATCH 1/2] f2fs: Apply bio flags to direct I/O Daniel Lee
2025-06-13 0:41 ` Chao Yu
2025-06-11 23:37 ` [PATCH 2/2] f2fs: use ioprio hint for hot and pinned files Daniel Lee
2025-06-13 0:47 ` Chao Yu
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=20250611233706.572784-1-chullee@google.com \
--to=chullee@google.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®