On Tue, 04 Jun 2024 11:05:22 +0800, libaokun@xxxxxxxxxxxxxxx wrote:
> Now we avoid throttling swap writes by determining whether the current
> process is kswapd (aka current_is_kswapd()), but swap writes can come
> from either kswapd or direct reclaim, so the swap writes from direct
> reclaim will still be throttled.
>
> When a process holds a lock to allocate a free page, and enters direct
> reclaim because there is no free memory, then it might trigger a hung
> due to the wbt throttling that causes other processes to fail to get
> the lock.
>
> [...]
Applied, thanks!
[1/1] blk-wbt: don't throttle swap writes in direct reclaim
commit: 4e63aeb5d0101ddada36a2f64f048e2f9d2202fc
Best regards,
--
Jens Axboe
