[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <15d07953-aeff-460e-81fe-ea7fc2f6145d@kernel.org>
Date: Thu, 25 Jan 2024 18:54:28 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: Zhaoyang Huang <huangzhaoyang@...il.com>
Cc: "zhaoyang.huang" <zhaoyang.huang@...soc.com>,
Andrew Morton <akpm@...ux-foundation.org>, Jens Axboe <axboe@...nel.dk>,
Yu Zhao <yuzhao@...gle.com>, Niklas Cassel <niklas.cassel@....com>,
"Martin K . Petersen" <martin.petersen@...cle.com>,
Hannes Reinecke <hare@...e.de>, Linus Walleij <linus.walleij@...aro.org>,
linux-mm@...ck.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, steve.kang@...soc.com
Subject: Re: [PATCHv3 1/1] block: introduce content activity based ioprio
On 1/25/24 18:37, Zhaoyang Huang wrote:
> Actually, the activity information comes from page's history (recorded
> at page cache's slot) instead of user space in step(1) and can be
> associate with bio in step(2) or iterate the bio in step(3)
> page fault(or vfs)(1)
> |
> alloc_pages
> |
> add_page_to_pagecache(get the page's activity information)
> |
> fs_readpage
> |
> bio_add_page(2)
> |
set your prio here. No change to the block layer needed. That is FS land.
> submit_bio(3)
--
Damien Le Moal
Western Digital Research
Powered by blists - more mailing lists