From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752248AbaFXHro (ORCPT ); Tue, 24 Jun 2014 03:47:44 -0400 Received: from lgeamrelo04.lge.com ([156.147.1.127]:43249 "EHLO lgeamrelo04.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751242AbaFXHrm (ORCPT ); Tue, 24 Jun 2014 03:47:42 -0400 X-Original-SENDERIP: 10.177.220.145 X-Original-MAILFROM: iamjoonsoo.kim@lge.com Date: Tue, 24 Jun 2014 16:52:23 +0900 From: Joonsoo Kim To: Andrew Morton Cc: Marek Szyprowski , "Aneesh Kumar K.V" , Michal Nazarewicz , Minchan Kim , Russell King - ARM Linux , Greg Kroah-Hartman , Paolo Bonzini , Gleb Natapov , Alexander Graf , Benjamin Herrenschmidt , Paul Mackerras , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Zhang Yanfei Subject: Re: [PATCH v3 -next 0/9] CMA: generalize CMA reserved area management code Message-ID: <20140624075223.GE4836@js1304-P5Q-DELUXE> References: <1402897251-23639-1-git-send-email-iamjoonsoo.kim@lge.com> <539EB4C7.3080106@samsung.com> <20140617012507.GA6825@js1304-P5Q-DELUXE> <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 18, 2014 at 01:51:44PM -0700, Andrew Morton wrote: > On Tue, 17 Jun 2014 10:25:07 +0900 Joonsoo Kim wrote: > > > > >v2: > > > > - Although this patchset looks very different with v1, the end result, > > > > that is, mm/cma.c is same with v1's one. So I carry Ack to patch 6-7. > > > > > > > >This patchset is based on linux-next 20140610. > > > > > > Thanks for taking care of this. I will test it with my setup and if > > > everything goes well, I will take it to my -next tree. If any branch > > > is required for anyone to continue his works on top of those patches, > > > let me know, I will also prepare it. > > > > Hello, > > > > I'm glad to hear that. :) > > But, there is one concern. As you already know, I am preparing further > > patches (Aggressively allocate the pages on CMA reserved memory). It > > may be highly related to MM branch and also slightly depends on this CMA > > changes. In this case, what is the best strategy to merge this > > patchset? IMHO, Anrew's tree is more appropriate branch. If there is > > no issue in this case, I am willing to develope further patches based > > on your tree. > > That's probably easier. Marek, I'll merge these into -mm (and hence > -next and git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git) > and shall hold them pending you review/ack/test/etc, OK? Hello, Marek. Could you share your decision about this patchset? Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by kanga.kvack.org (Postfix) with ESMTP id 3ABE36B0062 for ; Tue, 24 Jun 2014 03:47:43 -0400 (EDT) Received: by mail-pd0-f177.google.com with SMTP id y10so6590854pdj.8 for ; Tue, 24 Jun 2014 00:47:42 -0700 (PDT) Received: from lgeamrelo04.lge.com (lgeamrelo04.lge.com. [156.147.1.127]) by mx.google.com with ESMTP id wk8si25119598pab.59.2014.06.24.00.47.41 for ; Tue, 24 Jun 2014 00:47:42 -0700 (PDT) Date: Tue, 24 Jun 2014 16:52:23 +0900 From: Joonsoo Kim Subject: Re: [PATCH v3 -next 0/9] CMA: generalize CMA reserved area management code Message-ID: <20140624075223.GE4836@js1304-P5Q-DELUXE> References: <1402897251-23639-1-git-send-email-iamjoonsoo.kim@lge.com> <539EB4C7.3080106@samsung.com> <20140617012507.GA6825@js1304-P5Q-DELUXE> <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Morton Cc: Marek Szyprowski , "Aneesh Kumar K.V" , Michal Nazarewicz , Minchan Kim , Russell King - ARM Linux , Greg Kroah-Hartman , Paolo Bonzini , Gleb Natapov , Alexander Graf , Benjamin Herrenschmidt , Paul Mackerras , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Zhang Yanfei On Wed, Jun 18, 2014 at 01:51:44PM -0700, Andrew Morton wrote: > On Tue, 17 Jun 2014 10:25:07 +0900 Joonsoo Kim wrote: > > > > >v2: > > > > - Although this patchset looks very different with v1, the end result, > > > > that is, mm/cma.c is same with v1's one. So I carry Ack to patch 6-7. > > > > > > > >This patchset is based on linux-next 20140610. > > > > > > Thanks for taking care of this. I will test it with my setup and if > > > everything goes well, I will take it to my -next tree. If any branch > > > is required for anyone to continue his works on top of those patches, > > > let me know, I will also prepare it. > > > > Hello, > > > > I'm glad to hear that. :) > > But, there is one concern. As you already know, I am preparing further > > patches (Aggressively allocate the pages on CMA reserved memory). It > > may be highly related to MM branch and also slightly depends on this CMA > > changes. In this case, what is the best strategy to merge this > > patchset? IMHO, Anrew's tree is more appropriate branch. If there is > > no issue in this case, I am willing to develope further patches based > > on your tree. > > That's probably easier. Marek, I'll merge these into -mm (and hence > -next and git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git) > and shall hold them pending you review/ack/test/etc, OK? Hello, Marek. Could you share your decision about this patchset? Thanks. -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lgeamrelo04.lge.com (lgeamrelo04.lge.com [156.147.1.127]) by lists.ozlabs.org (Postfix) with ESMTP id 6CC371A0221 for ; Tue, 24 Jun 2014 17:47:43 +1000 (EST) Date: Tue, 24 Jun 2014 16:52:23 +0900 From: Joonsoo Kim To: Andrew Morton Subject: Re: [PATCH v3 -next 0/9] CMA: generalize CMA reserved area management code Message-ID: <20140624075223.GE4836@js1304-P5Q-DELUXE> References: <1402897251-23639-1-git-send-email-iamjoonsoo.kim@lge.com> <539EB4C7.3080106@samsung.com> <20140617012507.GA6825@js1304-P5Q-DELUXE> <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> Cc: kvm-ppc@vger.kernel.org, Russell King - ARM Linux , kvm@vger.kernel.org, linux-mm@kvack.org, Gleb Natapov , Greg Kroah-Hartman , Alexander Graf , Michal Nazarewicz , linux-kernel@vger.kernel.org, Minchan Kim , Paul Mackerras , "Aneesh Kumar K.V" , Paolo Bonzini , Zhang Yanfei , linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, Marek Szyprowski List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Jun 18, 2014 at 01:51:44PM -0700, Andrew Morton wrote: > On Tue, 17 Jun 2014 10:25:07 +0900 Joonsoo Kim wrote: > > > > >v2: > > > > - Although this patchset looks very different with v1, the end result, > > > > that is, mm/cma.c is same with v1's one. So I carry Ack to patch 6-7. > > > > > > > >This patchset is based on linux-next 20140610. > > > > > > Thanks for taking care of this. I will test it with my setup and if > > > everything goes well, I will take it to my -next tree. If any branch > > > is required for anyone to continue his works on top of those patches, > > > let me know, I will also prepare it. > > > > Hello, > > > > I'm glad to hear that. :) > > But, there is one concern. As you already know, I am preparing further > > patches (Aggressively allocate the pages on CMA reserved memory). It > > may be highly related to MM branch and also slightly depends on this CMA > > changes. In this case, what is the best strategy to merge this > > patchset? IMHO, Anrew's tree is more appropriate branch. If there is > > no issue in this case, I am willing to develope further patches based > > on your tree. > > That's probably easier. Marek, I'll merge these into -mm (and hence > -next and git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git) > and shall hold them pending you review/ack/test/etc, OK? Hello, Marek. Could you share your decision about this patchset? Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 From: iamjoonsoo.kim@lge.com (Joonsoo Kim) Date: Tue, 24 Jun 2014 16:52:23 +0900 Subject: [PATCH v3 -next 0/9] CMA: generalize CMA reserved area management code In-Reply-To: <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> References: <1402897251-23639-1-git-send-email-iamjoonsoo.kim@lge.com> <539EB4C7.3080106@samsung.com> <20140617012507.GA6825@js1304-P5Q-DELUXE> <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> Message-ID: <20140624075223.GE4836@js1304-P5Q-DELUXE> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Jun 18, 2014 at 01:51:44PM -0700, Andrew Morton wrote: > On Tue, 17 Jun 2014 10:25:07 +0900 Joonsoo Kim wrote: > > > > >v2: > > > > - Although this patchset looks very different with v1, the end result, > > > > that is, mm/cma.c is same with v1's one. So I carry Ack to patch 6-7. > > > > > > > >This patchset is based on linux-next 20140610. > > > > > > Thanks for taking care of this. I will test it with my setup and if > > > everything goes well, I will take it to my -next tree. If any branch > > > is required for anyone to continue his works on top of those patches, > > > let me know, I will also prepare it. > > > > Hello, > > > > I'm glad to hear that. :) > > But, there is one concern. As you already know, I am preparing further > > patches (Aggressively allocate the pages on CMA reserved memory). It > > may be highly related to MM branch and also slightly depends on this CMA > > changes. In this case, what is the best strategy to merge this > > patchset? IMHO, Anrew's tree is more appropriate branch. If there is > > no issue in this case, I am willing to develope further patches based > > on your tree. > > That's probably easier. Marek, I'll merge these into -mm (and hence > -next and git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git) > and shall hold them pending you review/ack/test/etc, OK? Hello, Marek. Could you share your decision about this patchset? Thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joonsoo Kim Date: Tue, 24 Jun 2014 07:52:23 +0000 Subject: Re: [PATCH v3 -next 0/9] CMA: generalize CMA reserved area management code Message-Id: <20140624075223.GE4836@js1304-P5Q-DELUXE> List-Id: References: <1402897251-23639-1-git-send-email-iamjoonsoo.kim@lge.com> <539EB4C7.3080106@samsung.com> <20140617012507.GA6825@js1304-P5Q-DELUXE> <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> In-Reply-To: <20140618135144.297c785260f9e2aebead867c@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andrew Morton Cc: Marek Szyprowski , "Aneesh Kumar K.V" , Michal Nazarewicz , Minchan Kim , Russell King - ARM Linux , Greg Kroah-Hartman , Paolo Bonzini , Gleb Natapov , Alexander Graf , Benjamin Herrenschmidt , Paul Mackerras , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Zhang Yanfei On Wed, Jun 18, 2014 at 01:51:44PM -0700, Andrew Morton wrote: > On Tue, 17 Jun 2014 10:25:07 +0900 Joonsoo Kim wrote: > > > > >v2: > > > > - Although this patchset looks very different with v1, the end result, > > > > that is, mm/cma.c is same with v1's one. So I carry Ack to patch 6-7. > > > > > > > >This patchset is based on linux-next 20140610. > > > > > > Thanks for taking care of this. I will test it with my setup and if > > > everything goes well, I will take it to my -next tree. If any branch > > > is required for anyone to continue his works on top of those patches, > > > let me know, I will also prepare it. > > > > Hello, > > > > I'm glad to hear that. :) > > But, there is one concern. As you already know, I am preparing further > > patches (Aggressively allocate the pages on CMA reserved memory). It > > may be highly related to MM branch and also slightly depends on this CMA > > changes. In this case, what is the best strategy to merge this > > patchset? IMHO, Anrew's tree is more appropriate branch. If there is > > no issue in this case, I am willing to develope further patches based > > on your tree. > > That's probably easier. Marek, I'll merge these into -mm (and hence > -next and git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git) > and shall hold them pending you review/ack/test/etc, OK? Hello, Marek. Could you share your decision about this patchset? Thanks.