lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 22 May 2024 11:57:32 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Bart Van Assche <bvanassche@....org>,
 Yunlong Xing <yunlong.xing@...soc.com>, 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 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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ