Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755960Ab2FZJRt (ORCPT ); Tue, 26 Jun 2012 05:17:49 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:46837 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754850Ab2FZJRr (ORCPT ); Tue, 26 Jun 2012 05:17:47 -0400 Date: Tue, 26 Jun 2012 02:17:45 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Glauber Costa cc: cgroups@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , linux-kernel@vger.kernel.org, Frederic Weisbecker , Pekka Enberg , Michal Hocko , Johannes Weiner , Christoph Lameter , devel@openvz.org, kamezawa.hiroyu@jp.fujitsu.com, Tejun Heo , Suleiman Souhlal Subject: Re: [PATCH 02/11] memcg: Reclaim when more than one page needed. In-Reply-To: <4FE97C20.8010500@parallels.com> Message-ID: References: <1340633728-12785-1-git-send-email-glommer@parallels.com> <1340633728-12785-3-git-send-email-glommer@parallels.com> <4FE960D6.4040409@parallels.com> <4FE97C20.8010500@parallels.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1408 Lines: 42 On Tue, 26 Jun 2012, Glauber Costa wrote: > > Nope, have you checked the output of /sys/kernel/slab/.../order when > > running slub? On my workstation 127 out of 316 caches have order-2 or > > higher by default. > > > > Well, this is still on the side of my argument, since this is still a majority > of them being low ordered. Ok, so what happens if I pass slub_min_order=2 on the command line? We never retry? > The code here does not necessarily have to retry - > if I understand it correctly - we just retry for very small allocations > because that is where our likelihood of succeeding is. > Well, the comment for NR_PAGES_TO_RETRY says /* * We need a number that is small enough to be likely to have been * reclaimed even under pressure, but not too big to trigger unnecessary * retries */ and mmzone.h says /* * PAGE_ALLOC_COSTLY_ORDER is the order at which allocations are deemed * costly to service. That is between allocation orders which should * coalesce naturally under reasonable reclaim pressure and those which * will not. */ #define PAGE_ALLOC_COSTLY_ORDER 3 so I'm trying to reconcile which one is correct. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/