[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5166bc31-1fd9-4f7f-bc51-f1f50d9d5483@acm.org>
Date: Wed, 22 May 2024 10:38:26 -0700
From: Bart Van Assche <bvanassche@....org>
To: Yunlong Xing <yunlong.xing@...soc.com>, axboe@...nel.dk,
yunlongxing23@...il.com, niuzhiguo84@...il.com, Hao_hao.Wang@...soc.com
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] loop: inherit the ioprio in loop woker thread
On 5/22/24 00:48, Yunlong Xing wrote:
> @@ -1913,6 +1921,10 @@ static void loop_handle_cmd(struct loop_cmd *cmd)
> set_active_memcg(old_memcg);
> css_put(cmd_memcg_css);
> }
> +
> + if (ori_ioprio != cmd_ioprio)
> + set_task_ioprio(current, ori_ioprio);
> +
> failed:
> /* complete non-aio request */
> if (!use_aio || ret) {
Does adding this call in the hot path have a measurable performance impact?
Thanks,
Bart.
Powered by blists - more mailing lists