Re: [PATCH] Docs/mm: document the OOM killer

[Michal Hocko <mhocko@suse.com>]

On Sun 15-03-26 20:48:22, Lorenzo Stoakes (Oracle) wrote:
> NAK for being AI slop again, obviously.
> 
> Again, +cc the OOM maintainer you failed to bother to look up.

Thanks!

> Reasons, as the rest:
> - Worthless documentation
> - Everything about patch screams 'zero effort, Claude did it all'
> - Bad etiquette
> 
> As with all the rest it'd need to be totally rewritten and it's not worth the
> maintainer time.
> 
> On Sat, Mar 14, 2026 at 04:25:18PM +0100, Kit Dallege wrote:
> > Fill in the oom.rst stub that was created in commit 481cc97349d6
> > ("mm,doc: Add new documentation structure") as part of the structured
> > memory management documentation following Mel Gorman's book outline.
> 
> I mean the more I see it the more annoying it is.
> 
> >
> > Cover the scoring heuristic, allocation constraints, OOM reaper,
> > process_mrelease syscall, and sysctl knobs.
> 
> This sentence contains almost as much content as the patch.

The real question is who is the expected audience of this documentation?
Administrators, kernel developers? 
Reading through this proposal this doesn't really seem to fit neither
well. For kernel developers who try to wrap their heads around the code
it is barely scratches the surface. For admins it doesn't really explain
more than an existing documentation for tunables.

So if there is a serious interest to make this useful kernel developers
oriented documentation I am more than willing to help. The code is not
really easy to follow as it is scattered. There are many subtle
expectations spread out and it is quite easy to break a delicate balance
tuned for through years. So there is a big documentatin gap I never got
around to fill up.

-- 
Michal Hocko
SUSE Labs