Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932974Ab1ELXvg (ORCPT ); Thu, 12 May 2011 19:51:36 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:38365 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932950Ab1ELXvc (ORCPT ); Thu, 12 May 2011 19:51:32 -0400 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Fri, 13 May 2011 08:44:31 +0900 From: KAMEZAWA Hiroyuki To: Johannes Weiner Cc: Daisuke Nishimura , Balbir Singh , Ying Han , Michal Hocko , Andrew Morton , Rik van Riel , Minchan Kim , KOSAKI Motohiro , Mel Gorman , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [rfc patch 1/6] memcg: remove unused retry signal from reclaim Message-Id: <20110513084431.937d72e9.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <1305212038-15445-2-git-send-email-hannes@cmpxchg.org> References: <1305212038-15445-1-git-send-email-hannes@cmpxchg.org> <1305212038-15445-2-git-send-email-hannes@cmpxchg.org> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 3.1.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 837 Lines: 22 On Thu, 12 May 2011 16:53:53 +0200 Johannes Weiner wrote: > If the memcg reclaim code detects the target memcg below its limit it > exits and returns a guaranteed non-zero value so that the charge is > retried. > > Nowadays, the charge side checks the memcg limit itself and does not > rely on this non-zero return value trick. > > This patch removes it. The reclaim code will now always return the > true number of pages it reclaimed on its own. > > Signed-off-by: Johannes Weiner Acked-by: KAMEZAWA Hiroyuki -- 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/