Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759819AbZDHBAp (ORCPT ); Tue, 7 Apr 2009 21:00:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753335AbZDHBAg (ORCPT ); Tue, 7 Apr 2009 21:00:36 -0400 Received: from cn.fujitsu.com ([222.73.24.84]:49349 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753293AbZDHBAg (ORCPT ); Tue, 7 Apr 2009 21:00:36 -0400 Message-ID: <49DBF653.7070101@cn.fujitsu.com> Date: Wed, 08 Apr 2009 08:56:51 +0800 From: Miao Xie Reply-To: miaox@cn.fujitsu.com User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Christoph Lameter CC: Ingo Molnar , Peter Zijlstra , Paul Menage , Nick Piggin , Linux-Kernel , Linux-MM , Yasunori Goto Subject: Re: [RFC][PATCH 0/3] cpuset,mm: fix memory spread bug References: <49DB306A.8070407@cn.fujitsu.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2072 Lines: 57 on 2009-4-8 5:04 Christoph Lameter wrote: > Interesting patch set but I cannot find parts 2 and 3. The locking changes > get rid of the generation scheme in cpusets which is a good thing if it > works right. Sorry for the late reply and my mistake. The following URLs is the patches' address. patch 1: restructure the function cpuset_update_task_memory_state() http://marc.info/?l=linux-kernel&m=123910183705576&w=2 patch 2: update tasks' page/slab spread flags in time http://marc.info/?l=linux-kernel&m=123910199505770&w=2 patch 3: update tasks' mems_allowed in time http://marc.info/?l=linux-mm&m=123910199605776&w=2 Thanks Miao > > On Tue, 7 Apr 2009, Miao Xie wrote: > >> The kernel still allocated the page caches on old node after modifying its >> cpuset's mems when 'memory_spread_page' was set, or it didn't spread the page >> cache evenly over all the nodes that faulting task is allowed to usr after >> memory_spread_page was set. it is caused by the old mem_allowed and flags >> of the task, the current kernel doesn't updates them unless some function >> invokes cpuset_update_task_memory_state(), it is too late sometimes.We must >> update the mem_allowed and the flags of the tasks in time. >> >> Slab has the same problem. >> >> The following patches fix this bug by updating tasks' mem_allowed and spread >> flag after its cpuset's mems or spread flag is changed. >> >> patch 1: restructure the function cpuset_update_task_memory_state() >> patch 2: update tasks' page/slab spread flags in time >> patch 3: update tasks' mems_allowed in time >> >> >> -- >> To unsubscribe, send a message with 'unsubscribe linux-mm' in >> the body to majordomo@kvack.org. For more info on Linux MM, >> see: http://www.linux-mm.org/ . >> Don't email: email@kvack.org >> > > > -- 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/