linux-kernel - Re: [PATCH -next] blk-wbt: don't throttle swap writes in direct reclaim

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] [day] [month] [year] [list]

Message-Id: <171983840672.13284.3665627911402096359.b4-ty@kernel.dk>
Date: Mon, 01 Jul 2024 06:53:26 -0600
From: Jens Axboe <axboe@...nel.dk>
To: linux-block@...r.kernel.org, libaokun@...weicloud.com
Cc: hch@...radead.org, linux-kernel@...r.kernel.org, yangerkun@...wei.com, 
 houtao1@...wei.com, yukuai3@...wei.com, libaokun1@...wei.com
Subject: Re: [PATCH -next] blk-wbt: don't throttle swap writes in direct
 reclaim


On Tue, 04 Jun 2024 11:05:22 +0800, libaokun@...weicloud.com 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