Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753868AbdLHWhX (ORCPT ); Fri, 8 Dec 2017 17:37:23 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:52906 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753666AbdLHWhV (ORCPT ); Fri, 8 Dec 2017 17:37:21 -0500 Date: Fri, 8 Dec 2017 14:37:19 -0800 From: Andrew Morton To: js1304@gmail.com Cc: Rik van Riel , Johannes Weiner , Laura Abbott , Minchan Kim , Marek Szyprowski , Michal Nazarewicz , "Aneesh Kumar K . V" , Vlastimil Babka , Russell King , Will Deacon , linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-team@lge.com, Joonsoo Kim , Tony Lindgren , Michal Hocko Subject: Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE Message-Id: <20171208143719.901b742d5238b829edac3b14@linux-foundation.org> In-Reply-To: <1512114786-5085-1-git-send-email-iamjoonsoo.kim@lge.com> References: <1512114786-5085-1-git-send-email-iamjoonsoo.kim@lge.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) 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 Content-Length: 1496 Lines: 40 On Fri, 1 Dec 2017 16:53:03 +0900 js1304@gmail.com wrote: > From: Joonsoo Kim > > v2 > o previous failure in linux-next turned out that it's not the problem of > this patchset. It was caused by the wrong assumption by specific > architecture. > > lkml.kernel.org/r/20171114173719.GA28152@atomide.com > > o add missing cache flush to the patch "ARM: CMA: avoid double mapping > to the CMA area if CONFIG_HIGHMEM = y" > > > This patchset is the follow-up of the discussion about the > "Introduce ZONE_CMA (v7)" [1]. Please reference it if more information > is needed. > > In this patchset, the memory of the CMA area is managed by using > the ZONE_MOVABLE. Since there is another type of the memory in this zone, > we need to maintain a migratetype for the CMA memory to account > the number of the CMA memory. So, unlike previous patchset, there is > less deletion of the code. > > Otherwise, there is no big change. > > Motivation of this patchset is described in the commit description of > the patch "mm/cma: manage the memory of the CMA area by using > the ZONE_MOVABLE". Please refer it for more information. > > This patchset is based on linux-next-20170822 plus > "mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE". mhocko had issues with that patch which weren't addressed? http://lkml.kernel.org/r/20170914132452.d5klyizce72rhjaa@dhcp22.suse.cz > Thanks. > > [1]: lkml.kernel.org/r/1491880640-9944-1-git-send-email-iamjoonsoo.kim@lge.com