[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zbj_A3e1T1wRsKiM@casper.infradead.org>
Date: Tue, 30 Jan 2024 13:52:03 +0000
From: Matthew Wilcox <willy@...radead.org>
To: "zhaoyang.huang" <zhaoyang.huang@...soc.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Jens Axboe <axboe@...nel.dk>,
Yu Zhao <yuzhao@...gle.com>, Damien Le Moal <dlemoal@...nel.org>,
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-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
Zhaoyang Huang <huangzhaoyang@...il.com>, steve.kang@...soc.com
Subject: Re: [PATCHv5 1/1] block: introduce content activity based ioprio
On Tue, Jan 30, 2024 at 04:42:07PM +0800, zhaoyang.huang wrote:
> +static __maybe_unused
> +bool act_bio_add_folio(struct bio *bio, struct folio *folio, size_t len,
> + size_t off)
No, stop this. What the filesystem needs to do is not
s/bio_add_folio/act_bio_add_folio/. There needs to be an API to set the
bio prio; something like:
bio_set_active_prio(bio, folio);
and then you can do whatever gunk is needed in bio_set_active_prio()
to end up calling bio_set_prio().
Powered by blists - more mailing lists