lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20171208143719.901b742d5238b829edac3b14@linux-foundation.org> Date: Fri, 8 Dec 2017 14:37:19 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: js1304@...il.com Cc: Rik van Riel <riel@...hat.com>, Johannes Weiner <hannes@...xchg.org>, Laura Abbott <lauraa@...eaurora.org>, Minchan Kim <minchan@...nel.org>, Marek Szyprowski <m.szyprowski@...sung.com>, Michal Nazarewicz <mina86@...a86.com>, "Aneesh Kumar K . V" <aneesh.kumar@...ux.vnet.ibm.com>, Vlastimil Babka <vbabka@...e.cz>, Russell King <linux@...linux.org.uk>, Will Deacon <will.deacon@....com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, kernel-team@....com, Joonsoo Kim <iamjoonsoo.kim@....com>, Tony Lindgren <tony@...mide.com>, Michal Hocko <mhocko@...nel.org> Subject: Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE On Fri, 1 Dec 2017 16:53:03 +0900 js1304@...il.com wrote: > From: Joonsoo Kim <iamjoonsoo.kim@....com> > > 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@...mide.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@....com
Powered by blists - more mailing lists