Re: [PATCH 1/2] mm: vmscan: Split proactive reclaim statistics from direct reclaim statistics

[Michal Koutný]

Hello.

On Tue, Mar 18, 2025 at 03:58:32PM +0800, Hao Jia <jiahao.kernel@xxxxxxxxx> wrote:
> From: Hao Jia <jiahao1@xxxxxxxxxxx>
> 
> In proactive memory reclaim scenarios, it is necessary to
> accurately track proactive reclaim statistics to dynamically
> adjust the frequency and amount of memory being reclaimed
> proactively. Currently, proactive reclaim is included in
> direct reclaim statistics, which can make these
> direct reclaim statistics misleading.

How silly is it to have multiple memory.reclaim writers?
Would it make sense to bind those statistics to each such a write(r)
instead of the aggregated totals?

Michal

Attachment: signature.asc
Description: PGP signature