On 2022/11/18 11:46, Yangtao Li wrote:
Under the current logic, after the discard thread wakes up, it will not
run according to the expected policy, but will use the expected policy
before sleep. Move the strategy selection to after the thread wakes up,
so that the running state of the thread
HI Chao,
>> set_freezable();
>>
>> do {
>
> if (!atomic_read(>discard_cmd_cnt))
> wait_ms = dpolicy.max_interval;
dpolicy has not been initialized for the first time, and the value in the stack
is unstable.
Thx,
Yangtao
On 2022/11/18 11:46, Yangtao Li wrote:
Under the current logic, after the discard thread wakes up, it will not
run according to the expected policy, but will use the expected policy
before sleep. Move the strategy selection to after the thread wakes up,
so that the running state of the thread
