Received-SPF: pass (google.com: domain of linux-kernel+bounces-74267-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>
To: Jens Axboe <axboe@kernel.dk>, "Darrick J . Wong" <djwong@kernel.org>,
        Alexander Viro <viro@zeniv.linux.org.uk>,
        Christian Brauner
	<brauner@kernel.org>, <linux-block@vger.kernel.org>,
        <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        Zhaoyang
 Huang <huangzhaoyang@gmail.com>, <steve.kang@unisoc.com>
Subject: [PATCH 0/2] *** introduce content activity based ioprio ***
Date: Wed, 21 Feb 2024 15:53:36 +0800
Message-ID: <20240221075338.598280-1-zhaoyang.huang@unisoc.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain

From: Zhaoyang Huang <zhaoyang.huang@unisoc.com>

Currently, request's ioprio are set via task's schedule priority(when no
blkcg configured), which has high priority tasks possess the privilege on
both of CPU and IO scheduling. Furthermore, most of the write requestes
are launched asynchronosly from kworker which can't know the submitter's
priorities.
This commit works as a hint of original policy by promoting the request
ioprio based on the page/folio's activity. The original idea comes from
LRU_GEN which provides more precised folio activity than before. This
commit try to adjust the request's ioprio when certain part of its folios
are hot, which indicate that this request carry important contents and
need be scheduled ealier.

Zhaoyang Huang (2):
  block: introduce content activity based ioprio
  fs: introduce content activity based ioprio

 block/Kconfig          | 15 +++++++++++++++
 block/bio.c            | 34 ++++++++++++++++++++++++++++++++++
 fs/iomap/buffered-io.c |  3 +++
 fs/mpage.c             |  2 ++
 include/linux/bio.h    |  1 +
 5 files changed, 55 insertions(+)

-- 
2.25.1