Hmm. Thanks for looking into it (and the others). This is something
I noticed as a discrepancy in the source, rather than something from
which I observed any OOMs. So if you're already working on bringing
the global and memcg approaches into line, I defer to your judgement.
But it seems to me worrying and fragile while they diverge in this way.
If the global has anon, active anon, file, active file and unevictable
lrus for the page; and the memcg has anon, active anon, file, active file
and unevictable lrus for the page cgroup; but different choices are made
which to put on where, then we're heading for confusion and trouble.
And when called, __mem_cgroup_move_lists tries to keep the activ-ity of
the memcg lrus in step with the activ-ity of the global lrus, doesn't
it? So it's beyond my comprehension to start them off out of step.
Hugh
--
