From: Yi Sun <yi.sun@unisoc.com>
To: <sunyibuaa@gmail.com>, <tj@kernel.org>, <jiangshanlai@gmail.com>,
<jaegeuk@kernel.org>, <chao@kernel.org>
Cc: <ebiggers@google.com>, <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <kent.overstreet@linux.dev>,
<niuzhiguo84@gmail.com>, <Hao_hao.Wang@unisoc.com>,
<yunlongxing23@gmail.com>, <yi.sun@unisoc.com>
Subject: [PATCH v2 0/2] new struct io_work and use it in f2fs fsverity work
Date: Mon, 1 Jul 2024 15:51:36 +0800 [thread overview]
Message-ID: <20240701075138.1144575-1-yi.sun@unisoc.com> (raw)
Many works will go to submit_bio(). In many cases, the default
io priority of kworker cannot meet the real-time requirements of
the work. Such as f2fs_verify_bio work.
If a high-task-priority process reads the verity-file, it is
possible that the high-task-priority process will be slowly
because the kworker's io priority is too low.
A new work struct containing io priority can solve this problem.
Yi Sun (2):
workqueue: new struct io_work
f2fs: set io priority for fsverity work
fs/f2fs/data.c | 17 +++++++------
fs/f2fs/f2fs.h | 1 +
fs/f2fs/verity.c | 5 ++++
include/linux/workqueue.h | 47 ++++++++++++++++++++++++++++++++++++
kernel/workqueue.c | 50 +++++++++++++++++++++++++++++++++++++++
5 files changed, 113 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2024-07-01 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 7:51 Yi Sun [this message]
2024-07-01 7:51 ` [PATCH v2 1/2] workqueue: new struct io_work Yi Sun
2024-07-01 17:32 ` Tejun Heo
2024-07-02 3:53 ` Kent Overstreet
2024-07-02 9:27 ` yi sun
2024-07-02 16:40 ` Tejun Heo
2024-07-02 16:45 ` Kent Overstreet
2024-07-02 3:40 ` kernel test robot
2024-07-02 21:51 ` kernel test robot
2024-07-01 7:51 ` [PATCH v2 2/2] f2fs: set io priority for fsverity work Yi Sun
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=20240701075138.1144575-1-yi.sun@unisoc.com \
--to=yi.sun@unisoc.com \
--cc=Hao_hao.Wang@unisoc.com \
--cc=chao@kernel.org \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=sunyibuaa@gmail.com \
--cc=tj@kernel.org \
--cc=yunlongxing23@gmail.com \
/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®