mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yi Sun <yi.sun@unisoc.com>
To: <sunyibuaa@gmail.com>, <tj@kernel.org>, <jaegeuk@kernel.org>,
	<chao@kernel.org>
Cc: <ebiggers@google.com>, <jiangshanlai@gmail.com>,
	<kent.overstreet@linux.dev>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>, <niuzhiguo84@gmail.com>,
	<Hao_hao.Wang@unisoc.com>, <yunlongxing23@gmail.com>
Subject: [PATCH 0/2] add io priority feature to work and use it in f2fs fsverity work
Date: Fri, 21 Jun 2024 14:26:15 +0800	[thread overview]
Message-ID: <20240621062617.595007-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 likely
that the high-task-priority process will be slowly because the
kworker's io priority is too low.

Patch 1: Provide a set of interfaces for temporarily changing the
io priority of kworker.
Patch 2: Use the interfaces provided in patch1 to temporarily change
the io priority of f2fs_verify_bio work.

Yi Sun (2):
  workqueue: add io priority to work_struct
  f2fs: set f2fs verify work io priority

 fs/f2fs/data.c                  |  5 ++++
 include/linux/workqueue.h       |  9 ++++++
 include/linux/workqueue_types.h |  6 ++++
 kernel/workqueue.c              | 51 +++++++++++++++++++++++++++++++++
 4 files changed, 71 insertions(+)

-- 
2.25.1


             reply	other threads:[~2024-06-21  6:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21  6:26 Yi Sun [this message]
2024-06-21  6:26 ` [PATCH 1/2] workqueue: add io priority to work_struct Yi Sun
2024-06-21  8:00   ` Lai Jiangshan
2024-06-21 14:23   ` Kent Overstreet
2024-06-26  4:32   ` kernel test robot
2024-06-26  5:17   ` kernel test robot
2024-06-21  6:26 ` [PATCH 2/2] f2fs: set f2fs verify work io priority 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=20240621062617.595007-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®