On Fri, Aug 25, 2017 at 02:32:13PM -0700, Andrew Morton wrote: > On Thu, 24 Aug 2017 15:36:30 +0900 js1304@xxxxxxxxx wrote: > > > From: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> > > > > 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". > > > > But "mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE" did > not do very well at review - both Michal and Vlastimil are looking for > changes. So we're not ready for a patch series which depends upon that > one? Oops. I checked again and I found that this patchset is not dependant to that patch. It's just leftover from ZONE_CMA patchset. Thanks. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
