I've taken a brief read through the patch series. It's a noble effort, but from the light initial feedback there will a few rounds of rework before this is a ca

I've taken a brief read through the patch series. It's a noble effort, but from the light initial feedback there will a few rounds of rework before this is a candidate in a release. This also feels unlikely to be backported, given the numerous subtle changes (e.g. cgroups v1 incompatibilities, byte vs. page accounting). This really seems like a somewhat obvious caveat of SLUB, in hindsight at least, given how memory cgroups work. The accounting overhead here seems like opening a complexity can of worms. For memory-pressure intensive short-lived applications (e.g. Hadoop jobs with no strict NUMA affinity), this could net some real benefits when processes jump across cores, let alone physical cores. Most serious folks should be setting at least some CPU affinity anyways and discourage the scheduler from bouncing processes between cores, which otherwise exasperates the issue mitigated by this patch set. If you've ever wondered why you struggle to make use of all of your RAM on a large many-core host, this is potentially a big reason why.