Re: [PATCH v7 0/7] Introduce ZONE_CMA

> > > > Okay. We did a lot of discussion so it's better to summarise it. > > > > 1. ZONE_CMA might be a nicer solution than MIGRATETYPE. > > 2. Additional bit in page flags would cause another kind of > > maintenance problem so it's better to avoid it as much as possible. > > 3. Abusing

Re: [PATCH v7 0/7] Introduce ZONE_CMA

> > > > Okay. We did a lot of discussion so it's better to summarise it. > > > > 1. ZONE_CMA might be a nicer solution than MIGRATETYPE. > > 2. Additional bit in page flags would cause another kind of > > maintenance problem so it's better to avoid it as much as possible. > > 3. Abusing

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon 15-05-17 12:57:15, Joonsoo Kim wrote: > On Fri, May 12, 2017 at 08:38:15AM +0200, Michal Hocko wrote: [...] > > I really do not want to question your "simple test" but page_zonenum is > > used in many performance sensitive paths and proving it doesn't regress > > would require testing many

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon 15-05-17 12:57:15, Joonsoo Kim wrote: > On Fri, May 12, 2017 at 08:38:15AM +0200, Michal Hocko wrote: [...] > > I really do not want to question your "simple test" but page_zonenum is > > used in many performance sensitive paths and proving it doesn't regress > > would require testing many

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Fri, May 12, 2017 at 08:38:15AM +0200, Michal Hocko wrote: > On Fri 12-05-17 11:00:48, Joonsoo Kim wrote: > > On Thu, May 11, 2017 at 11:13:04AM +0200, Michal Hocko wrote: > > > On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > > > > Sorry for the late response. I was on a vacation. > > > > > > >

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Fri, May 12, 2017 at 08:38:15AM +0200, Michal Hocko wrote: > On Fri 12-05-17 11:00:48, Joonsoo Kim wrote: > > On Thu, May 11, 2017 at 11:13:04AM +0200, Michal Hocko wrote: > > > On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > > > > Sorry for the late response. I was on a vacation. > > > > > > >

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Fri 12-05-17 11:00:48, Joonsoo Kim wrote: > On Thu, May 11, 2017 at 11:13:04AM +0200, Michal Hocko wrote: > > On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > > > Sorry for the late response. I was on a vacation. > > > > > > On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > > > >

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Fri 12-05-17 11:00:48, Joonsoo Kim wrote: > On Thu, May 11, 2017 at 11:13:04AM +0200, Michal Hocko wrote: > > On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > > > Sorry for the late response. I was on a vacation. > > > > > > On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > > > >

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu, May 11, 2017 at 11:13:04AM +0200, Michal Hocko wrote: > On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > > Sorry for the late response. I was on a vacation. > > > > On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > > > On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > > > > On

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu, May 11, 2017 at 11:13:04AM +0200, Michal Hocko wrote: > On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > > Sorry for the late response. I was on a vacation. > > > > On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > > > On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > > > > On

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > Sorry for the late response. I was on a vacation. > > On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > > On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > > > On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: > > [...] > > > >

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu 11-05-17 11:12:43, Joonsoo Kim wrote: > Sorry for the late response. I was on a vacation. > > On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > > On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > > > On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: > > [...] > > > >

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 05/04/2017 02:46 PM, Michal Hocko wrote: > On Thu 04-05-17 14:33:24, Vlastimil Babka wrote: >>> >>> I am pretty sure s390 and ppc support NUMA and aim at supporting really >>> large systems. >> >> I don't see ppc there, > > config KVM_BOOK3S_64_HV > tristate "KVM for POWER7 and later

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 05/04/2017 02:46 PM, Michal Hocko wrote: > On Thu 04-05-17 14:33:24, Vlastimil Babka wrote: >>> >>> I am pretty sure s390 and ppc support NUMA and aim at supporting really >>> large systems. >> >> I don't see ppc there, > > config KVM_BOOK3S_64_HV > tristate "KVM for POWER7 and later

Re: [PATCH v7 0/7] Introduce ZONE_CMA

Sorry for the late response. I was on a vacation. On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > > On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: > [...] > > > I see this point and I agree that using a specific zone

Re: [PATCH v7 0/7] Introduce ZONE_CMA

Sorry for the late response. I was on a vacation. On Tue, May 02, 2017 at 03:32:29PM +0200, Michal Hocko wrote: > On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > > On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: > [...] > > > I see this point and I agree that using a specific zone

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu 04-05-17 14:33:24, Vlastimil Babka wrote: > On 05/02/2017 03:03 PM, Michal Hocko wrote: > > On Tue 02-05-17 10:06:01, Vlastimil Babka wrote: > >> On 04/27/2017 05:06 PM, Michal Hocko wrote: > >>> On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > On Mon, Apr 24, 2017 at 03:09:36PM +0200,

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu 04-05-17 14:33:24, Vlastimil Babka wrote: > On 05/02/2017 03:03 PM, Michal Hocko wrote: > > On Tue 02-05-17 10:06:01, Vlastimil Babka wrote: > >> On 04/27/2017 05:06 PM, Michal Hocko wrote: > >>> On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > On Mon, Apr 24, 2017 at 03:09:36PM +0200,

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 05/02/2017 03:03 PM, Michal Hocko wrote: > On Tue 02-05-17 10:06:01, Vlastimil Babka wrote: >> On 04/27/2017 05:06 PM, Michal Hocko wrote: >>> On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > On Mon 17-04-17 11:02:12, Joonsoo

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 05/02/2017 03:03 PM, Michal Hocko wrote: > On Tue 02-05-17 10:06:01, Vlastimil Babka wrote: >> On 04/27/2017 05:06 PM, Michal Hocko wrote: >>> On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > On Mon 17-04-17 11:02:12, Joonsoo

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 02/05/17 16:03, Michal Hocko wrote: > I can imagine that we could make ZONE_CMA configurable in a way that > only very well defined use cases would be supported so that we can save > page flags space. But this alone sounds like a maintainability nightmare > to me. Especially when I consider

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 02/05/17 16:03, Michal Hocko wrote: > I can imagine that we could make ZONE_CMA configurable in a way that > only very well defined use cases would be supported so that we can save > page flags space. But this alone sounds like a maintainability nightmare > to me. Especially when I consider

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: [...] > > I see this point and I agree that using a specific zone might be a > > _nicer_ solution in the end but you have to consider another aspects as > > well. The main one I am worried

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 02-05-17 13:01:32, Joonsoo Kim wrote: > On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: [...] > > I see this point and I agree that using a specific zone might be a > > _nicer_ solution in the end but you have to consider another aspects as > > well. The main one I am worried

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 02-05-17 10:06:01, Vlastimil Babka wrote: > On 04/27/2017 05:06 PM, Michal Hocko wrote: > > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > >> On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > >>> On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > On Thu, Apr 13, 2017 at

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 02-05-17 10:06:01, Vlastimil Babka wrote: > On 04/27/2017 05:06 PM, Michal Hocko wrote: > > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > >> On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > >>> On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > On Thu, Apr 13, 2017 at

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 04/27/2017 05:06 PM, Michal Hocko wrote: > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: >> On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: >>> On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > On Wed 12-04-17

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 04/27/2017 05:06 PM, Michal Hocko wrote: > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: >> On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: >>> On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > On Wed 12-04-17

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > > On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > > > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: >

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote: > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > > On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > > > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: >

Re: Generic approach to customizable zones - was: Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 28/04/17 11:36, Michal Hocko wrote: > I didn't read this thoughly yet because I will be travelling shortly ok, thanks for bearing with me =) > but > this point alone just made ask, because it seems there is some > misunderstanding It is possible, so far I did some changes, but I have not

Re: Generic approach to customizable zones - was: Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 28/04/17 11:36, Michal Hocko wrote: > I didn't read this thoughly yet because I will be travelling shortly ok, thanks for bearing with me =) > but > this point alone just made ask, because it seems there is some > misunderstanding It is possible, so far I did some changes, but I have not

Re: Generic approach to customizable zones - was: Re: [PATCH v7 0/7] Introduce ZONE_CMA

I didn't read this thoughly yet because I will be travelling shortly but this point alone just made ask, because it seems there is some misunderstanding On Fri 28-04-17 11:04:27, Igor Stoppa wrote: [...] > * if one is happy to have a 64bits type, allow for as many zones as > it's possible to

Re: Generic approach to customizable zones - was: Re: [PATCH v7 0/7] Introduce ZONE_CMA

I didn't read this thoughly yet because I will be travelling shortly but this point alone just made ask, because it seems there is some misunderstanding On Fri 28-04-17 11:04:27, Igor Stoppa wrote: [...] > * if one is happy to have a 64bits type, allow for as many zones as > it's possible to

Generic approach to customizable zones - was: Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 27/04/17 18:06, Michal Hocko wrote: > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: [...] >> Yes, it requires one more bit for a new zone and it's handled by the patch. > > I am pretty sure that you are aware that consuming new page flag bits > is usually a no-go and something we try to avoid

Generic approach to customizable zones - was: Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 27/04/17 18:06, Michal Hocko wrote: > On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: [...] >> Yes, it requires one more bit for a new zone and it's handled by the patch. > > I am pretty sure that you are aware that consuming new page flag bits > is usually a no-go and something we try to avoid

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: [...] > > not for

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: [...] > > not for

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > [...] > > > > ZONE_CMA is conceptually the same with ZONE_MOVABLE.

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > [...] > > > > ZONE_CMA is conceptually the same with ZONE_MOVABLE.

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: [...] > > > ZONE_CMA is conceptually the same with ZONE_MOVABLE. There is a software > > > constraint to guarantee the success of future

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: [...] > > > ZONE_CMA is conceptually the same with ZONE_MOVABLE. There is a software > > > constraint to guarantee the success of future

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 2017/4/11 11:17, js1...@gmail.com wrote: > From: Joonsoo Kim > > Changed from v6 > o Rebase on next-20170405 > o Add a fix for lowmem mapping on ARM (last patch) > o Re-organize the cover letter > > Changes from v5 > o Rebase on next-20161013 > o Cosmetic change on

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On 2017/4/11 11:17, js1...@gmail.com wrote: > From: Joonsoo Kim > > Changed from v6 > o Rebase on next-20170405 > o Add a fix for lowmem mapping on ARM (last patch) > o Re-organize the cover letter > > Changes from v5 > o Rebase on next-20161013 > o Cosmetic change on patch 1 > o Optimize span

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Fri 21-04-17 10:35:03, Joonsoo Kim wrote: [...] > Hello, Michal. > > If you don't have any more question, I will send next version with > updated cover-letter. I am sorry but I am bussy as hell this week and didn't get to your email yet. I will try as soon as possible. -- Michal Hocko SUSE

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Fri 21-04-17 10:35:03, Joonsoo Kim wrote: [...] > Hello, Michal. > > If you don't have any more question, I will send next version with > updated cover-letter. I am sorry but I am bussy as hell this week and didn't get to your email yet. I will try as soon as possible. -- Michal Hocko SUSE

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon, Apr 17, 2017 at 11:02:12AM +0900, Joonsoo Kim wrote: > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > > > On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > > > > Hi, > > > > I didn't get to read though patches

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Mon, Apr 17, 2017 at 11:02:12AM +0900, Joonsoo Kim wrote: > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > > > On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > > > > Hi, > > > > I didn't get to read though patches

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > > On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > > > Hi, > > > I didn't get to read though patches yet but the cover letter didn't > > > really help me to understand the

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > > On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > > > Hi, > > > I didn't get to read though patches yet but the cover letter didn't > > > really help me to understand the

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > > Hi, > > I didn't get to read though patches yet but the cover letter didn't > > really help me to understand the basic concepts to have a good starting > > point before diving into

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: > On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > > Hi, > > I didn't get to read though patches yet but the cover letter didn't > > really help me to understand the basic concepts to have a good starting > > point before diving into

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue, Apr 11, 2017 at 12:17:13PM +0900, js1...@gmail.com wrote: > From: Joonsoo Kim > > Changed from v6 > o Rebase on next-20170405 > o Add a fix for lowmem mapping on ARM (last patch) Hello, Russell and Will. In this 7th patchset, I newly added a patch for ARM. Could

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue, Apr 11, 2017 at 12:17:13PM +0900, js1...@gmail.com wrote: > From: Joonsoo Kim > > Changed from v6 > o Rebase on next-20170405 > o Add a fix for lowmem mapping on ARM (last patch) Hello, Russell and Will. In this 7th patchset, I newly added a patch for ARM. Could you review it? Thanks.

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > Hi, > I didn't get to read though patches yet but the cover letter didn't > really help me to understand the basic concepts to have a good starting > point before diving into implementation details. It contains a lot of > history

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue, Apr 11, 2017 at 08:15:20PM +0200, Michal Hocko wrote: > Hi, > I didn't get to read though patches yet but the cover letter didn't > really help me to understand the basic concepts to have a good starting > point before diving into implementation details. It contains a lot of > history

Re: [PATCH v7 0/7] Introduce ZONE_CMA

Hi, I didn't get to read though patches yet but the cover letter didn't really help me to understand the basic concepts to have a good starting point before diving into implementation details. It contains a lot of history remarks which is not bad but IMHO too excessive here. I would appreciate the

Re: [PATCH v7 0/7] Introduce ZONE_CMA

Hi, I didn't get to read though patches yet but the cover letter didn't really help me to understand the basic concepts to have a good starting point before diving into implementation details. It contains a lot of history remarks which is not bad but IMHO too excessive here. I would appreciate the

[PATCH v7 0/7] Introduce ZONE_CMA

From: Joonsoo Kim Changed from v6 o Rebase on next-20170405 o Add a fix for lowmem mapping on ARM (last patch) o Re-organize the cover letter Changes from v5 o Rebase on next-20161013 o Cosmetic change on patch 1 o Optimize span of ZONE_CMA on multiple node system

[PATCH v7 0/7] Introduce ZONE_CMA

From: Joonsoo Kim Changed from v6 o Rebase on next-20170405 o Add a fix for lowmem mapping on ARM (last patch) o Re-organize the cover letter Changes from v5 o Rebase on next-20161013 o Cosmetic change on patch 1 o Optimize span of ZONE_CMA on multiple node system Changes from v4 o Rebase on