Re: [PATCH] mm, slub: print CPU id on slab OOM

[David Rientjes]

On Tue, 6 Aug 2024, Axel Rasmussen wrote:

> Depending on how remote_node_defrag_ratio is configured, allocations can
> end up in this path as a result of the local node being OOM, despite the
> allocation overall being unconstrained (node == -1).
> 
> When we print a warning, printing the current CPU makes that situation
> more clear (i.e., you can immediately see which node's OOM status
> matters for the allocation at hand).
> 
> Signed-off-by: Axel Rasmussen <axelrasmussen@xxxxxxxxxx>

Acked-by: David Rientjes <rientjes@xxxxxxxxxx>