linux-kernel - Re: MGLRU premature memcg OOM on slow writes

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]

Message-Id: <20240301112535.1609-1-hdanton@sina.com>
Date: Fri,  1 Mar 2024 19:25:35 +0800
From: Hillf Danton <hdanton@...a.com>
To: Axel Rasmussen <axelrasmussen@...gle.com>
Cc: chris@...isdown.name,
	hannes@...xchg.org,
	linux-kernel@...r.kernel.org,
	linux-mm@...ck.org,
	yuzhao@...gle.com
Subject: Re: MGLRU premature memcg OOM on slow writes

On Thu, 29 Feb 2024 15:51:33 -0800 Axel Rasmussen <axelrasmussen@...gle.com>
> 
> Yosry pointed out [1], where MGLRU used to call this but stopped doing that. It
> makes sense to me at least that doing writeback every time we age is too
> aggressive, but doing it in evict_folios() makes some sense to me, basically to
> copy the behavior the non-MGLRU path (shrink_inactive_list()) has.
> 
> I can send a patch which tries to implement this next week. In the meantime, Yu,

Better after working out why flusher failed to do the job, given background
writeback and balance_dirty_pages_ratelimited().
If pushing kswapd on the back makes any sense, what prevents you from pushing
flusher instead, given they are two different things by define?

> please let me know if what I've said here makes no sense for some reason. :)
> 
> [1]: https://lore.kernel.org/lkml/YzSiWq9UEER5LKup@google.com/