On Tue, 21 Feb 2012, Konstantin Khlebnikov wrote: > > But just one question: how appears uncharged pages in mem-cg lru lists? One way is swapin readahead pages, which cannot be charged to a memcg until they're "claimed"; but we do need them visible on lru, otherwise memory pressure couldn't reclaim them when necessary. Another way is simply that uncharging has not historically removed the page from lru list if it's on. I usually assume that's an optimization: why bother to get lru locks and take it off (and put it on the root lru? if we don't, we're assuming it's will be freed very shortly - I'm not sure that's always a good assumption), if freeing the page will usually do that for us (without having to change lrus). If I thought for longer, I might come up with other scenarios. > Maybe we can forbid this case and uncharge these pages right in > __page_cache_release() and release_pages() at final removing from LRU. > This is how my old mem-controller works. There pages in lru are always > charged. As things stand, that would mean lock_page_cgroup() has to disable irqs everywhere. I'm not sure of the further ramifications of moving uncharge to __page_cache_release() and release_pages(). I don't think a change like that is out of the question, but it's certainly a bigger change than I'd like to consider in this series. Hugh -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>