From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030300AbVJERvZ (ORCPT ); Wed, 5 Oct 2005 13:51:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030303AbVJERvZ (ORCPT ); Wed, 5 Oct 2005 13:51:25 -0400 Received: from e3.ny.us.ibm.com ([32.97.182.143]:56771 "EHLO e3.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1030302AbVJERvY (ORCPT ); Wed, 5 Oct 2005 13:51:24 -0400 Subject: Re: [PATCH 3/7] Fragmentation Avoidance V16: 003_fragcore From: Dave Hansen To: Mel Gorman Cc: linux-mm , Andrew Morton , kravetz@us.ibm.com, Linux Kernel Mailing List , jschopp@austin.ibm.com, lhms In-Reply-To: References: <20051005144546.11796.1154.sendpatchset@skynet.csn.ul.ie> <20051005144602.11796.53850.sendpatchset@skynet.csn.ul.ie> <1128530908.26009.28.camel@localhost> <1128532920.26009.43.camel@localhost> Content-Type: text/plain Date: Wed, 05 Oct 2005 10:51:10 -0700 Message-Id: <1128534670.26009.48.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2005-10-05 at 18:45 +0100, Mel Gorman wrote: > The problem is that by putting all the changes to this function in another > patch, the kernel will not build after applying 003_fragcore. I am > assuming that is bad. I think it makes sense to leave this patch as it is, > but have a 004_showfree patch that adds the type_names[] array and a more > detailed printout in show_free_areas. The remaining patches get bumped up > a number. > > Would you be happy with that? Seems reasonable to me. -- Dave From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e3.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j95HpMV9024750 for ; Wed, 5 Oct 2005 13:51:22 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j95HpMt2079504 for ; Wed, 5 Oct 2005 13:51:22 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j95HpMR7013507 for ; Wed, 5 Oct 2005 13:51:22 -0400 Subject: Re: [PATCH 3/7] Fragmentation Avoidance V16: 003_fragcore From: Dave Hansen In-Reply-To: References: <20051005144546.11796.1154.sendpatchset@skynet.csn.ul.ie> <20051005144602.11796.53850.sendpatchset@skynet.csn.ul.ie> <1128530908.26009.28.camel@localhost> <1128532920.26009.43.camel@localhost> Content-Type: text/plain Date: Wed, 05 Oct 2005 10:51:10 -0700 Message-Id: <1128534670.26009.48.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Mel Gorman Cc: linux-mm , Andrew Morton , kravetz@us.ibm.com, Linux Kernel Mailing List , jschopp@austin.ibm.com, lhms List-ID: On Wed, 2005-10-05 at 18:45 +0100, Mel Gorman wrote: > The problem is that by putting all the changes to this function in another > patch, the kernel will not build after applying 003_fragcore. I am > assuming that is bad. I think it makes sense to leave this patch as it is, > but have a 004_showfree patch that adds the type_names[] array and a more > detailed printout in show_free_areas. The remaining patches get bumped up > a number. > > Would you be happy with that? Seems reasonable to me. -- Dave -- 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