From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752686Ab1L1AIU (ORCPT ); Tue, 27 Dec 2011 19:08:20 -0500 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:38372 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751011Ab1L1AIQ (ORCPT ); Tue, 27 Dec 2011 19:08:16 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Wed, 28 Dec 2011 09:06:56 +0900 From: KAMEZAWA Hiroyuki To: Hillf Danton Cc: "Nikolay S." , Dave Chinner , Michal Hocko , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: Kswapd in 3.2.0-rc5 is a CPU hog Message-Id: <20111228090656.4b24f36d.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: References: <1324437036.4677.5.camel@hakkenden.homenet> <20111221095249.GA28474@tiehlicka.suse.cz> <20111221225512.GG23662@dastard> <1324630880.562.6.camel@rybalov.eng.ttk.net> <20111223102027.GB12731@dastard> <1324638242.562.15.camel@rybalov.eng.ttk.net> <20111223204503.GC12731@dastard> <1324808519.29243.8.camel@hakkenden.homenet> <20111227092052.f2b02637.kamezawa.hiroyu@jp.fujitsu.com> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 3.1.1 (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 On Tue, 27 Dec 2011 21:33:04 +0800 Hillf Danton wrote: > On Tue, Dec 27, 2011 at 8:20 AM, KAMEZAWA Hiroyuki > wrote: > > On Mon, 26 Dec 2011 20:35:46 +0800 > > Hillf Danton wrote: > > > >> On Sun, Dec 25, 2011 at 6:21 PM, Nikolay S. wrote: > >> > > >> > Uhm.., is this patch against 3.2-rc4? I can not apply it. There's no > >> > mem_cgroup_lru_del_list(), but void mem_cgroup_del_lru_list(). Should I > >> > place changes there? > >> > > >> > And also, -rc7 is here. May the problem be addressed as part of some > >> > ongoing work? Is there any reason to try -rc7 (the problem requires > >> > several days of uptime to become obvious)? > >> > > >> > >> Sorry, Nikolay, it is not based on the -next, nor on the -rc5(I assumed it was). > >> The following is based on -next, and if you want to test -rc5, please > >> grep MEM_CGROUP_ZSTAT mm/memcontrol.c and change it. > >> > >> Best regard > >> > > > > Hmm ? memcg is used ? Why do you consider this will be a help ? > > > > Hi Kame > > Please see the livelock at > https://lkml.org/lkml/2011/12/23/222 > > and if it is related to the hog here, please check if the following is > in right direction. > But linux-next and his 3.2-rc5 has totally different LRU design. 3.2-rc doesn't have unified memcg/global LRU and memcg doesn't affect kswapd behavior if not used. Thanks, -Kame > Thanks > Hillf > --- > > --- a/mm/memcontrol.c Mon Dec 26 20:34:38 2011 > +++ b/mm/memcontrol.c Tue Dec 27 20:05:12 2011 > @@ -3637,6 +3637,7 @@ static int mem_cgroup_force_empty_list(s > list = &mz->lruvec.lists[lru]; > > loop = MEM_CGROUP_ZSTAT(mz, lru); > + WARN_ON((long)loop < 0); > /* give some margin against EBUSY etc...*/ > loop += 256; > busy = NULL; > -- > 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/ >