From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>,
Yunlong Xing <yunlong.xing@unisoc.com>,
yunlongxing23@gmail.com, niuzhiguo84@gmail.com,
Hao_hao.Wang@unisoc.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] loop: inherit the ioprio in loop woker thread
Date: Wed, 22 May 2024 11:57:32 -0600 [thread overview]
Message-ID: <68cfbc08-6d39-4bc6-854d-5df0c94dbfd4@kernel.dk> (raw)
In-Reply-To: <5166bc31-1fd9-4f7f-bc51-f1f50d9d5483@acm.org>
On 5/22/24 11:38 AM, Bart Van Assche wrote:
> 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?
It's loop, I would not be concerned with overhead. But it does look pretty
bogus to modify the task ioprio from here.
--
Jens Axboe
next prev parent reply other threads:[~2024-05-22 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 7:48 [PATCH] loop: inherit the ioprio in loop woker thread Yunlong Xing
2024-05-22 17:38 ` Bart Van Assche
2024-05-22 17:57 ` Jens Axboe [this message]
2024-05-22 18:12 ` Bart Van Assche
2024-05-22 18:13 ` Jens Axboe
2024-05-23 2:15 ` yunlong xing
2024-05-23 6:04 ` yunlong xing
2024-05-23 13:04 ` Jens Axboe
2024-05-23 14:52 ` yunlong xing
2024-05-23 14:58 ` Jens Axboe
2024-05-24 5:26 ` yunlong xing
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=68cfbc08-6d39-4bc6-854d-5df0c94dbfd4@kernel.dk \
--to=axboe@kernel.dk \
--cc=Hao_hao.Wang@unisoc.com \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=yunlong.xing@unisoc.com \
--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