From: Daniel Lee via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH v2 0/2] f2fs: Fix DIO flags and add ioprio hint
Date: Sun, 15 Jun 2025 07:42:33 -0700 [thread overview]
Message-ID: <20250615144235.1836469-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.
---
Changes in v2:
- f2fs: Apply bio flags to direct I/O
- Changed f2fs_io_flags() to accept a direct inode pointer
- f2fs: use ioprio hint for hot and pinned files
- Removed an unnecessary f2fs_mark_inode_dirty_sync() call
Daniel Lee (2):
f2fs: Apply bio flags to direct I/O
f2fs: use ioprio hint for hot and pinned files
fs/f2fs/data.c | 10 +++++-----
fs/f2fs/f2fs.h | 20 ++++++++++++++++++++
fs/f2fs/file.c | 14 ++++++++++++++
fs/f2fs/namei.c | 11 +++++++----
4 files changed, 46 insertions(+), 9 deletions(-)
--
2.50.0.rc1.591.g9c95f17f64-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2025-06-15 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 14:42 Daniel Lee via Linux-f2fs-devel [this message]
2025-06-15 14:42 ` [f2fs-dev] [PATCH v2 1/2] f2fs: Apply bio flags to direct I/O Daniel Lee via Linux-f2fs-devel
2025-06-16 12:41 ` Chao Yu via Linux-f2fs-devel
2025-06-30 23:02 ` Daniel Lee via Linux-f2fs-devel
2025-06-15 14:42 ` [f2fs-dev] [PATCH v2 2/2] f2fs: use ioprio hint for hot and pinned files Daniel Lee via Linux-f2fs-devel
2025-06-16 12:50 ` Chao Yu via Linux-f2fs-devel
2025-06-30 22:56 ` Daniel Lee via Linux-f2fs-devel
2025-07-01 3:39 ` Chao Yu via Linux-f2fs-devel
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=20250615144235.1836469-1-chullee@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=chullee@google.com \
--cc=jaegeuk@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).