Re: [PATCH 11/11] mm: Isolate pages for immediate reclaim on theirown LRU

[Hugh Dickins]

Sorry, Mel, I've had to revert this patch (and its two little children)
from my 3.2.0-rc6-next-20111222 testing: you really do need a page flag
(or substitute) for your "immediate" lru.

How else can a del_page_from_lru[_list]() know whether to decrement
the count of the immediate or the inactive list?  page_lru() says to
decrement the count of the inactive list, so in due course that wraps
to a gigantic number, and then page reclaim livelocks trying to wring
pages out of an empty list.  It's the memcg case I've been hitting,
but presumably the same happens with global counts.

There is another such accounting bug in -next, been there longer and
not so easy to hit: I'm fairly sure it will turn out to be memcg
misaccounting a THPage somewhere, I'll have a look around shortly.

Hugh

p.s. Immediate?  Isn't that an odd name for a list of pages which are
not immediately freeable?  Maybe Rik's launder/laundry name would be
better: pages which are currently being cleaned.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/