[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <87pooqsa41.fsf@linux.vnet.ibm.com>
Date: Tue, 30 Aug 2016 18:10:46 +0530
From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To: js1304@...il.com, Andrew Morton <akpm@...ux-foundation.org>
Cc: Rik van Riel <riel@...hat.com>,
Johannes Weiner <hannes@...xchg.org>,
mgorman@...hsingularity.net, Laura Abbott <lauraa@...eaurora.org>,
Minchan Kim <minchan@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Michal Nazarewicz <mina86@...a86.com>,
Vlastimil Babka <vbabka@...e.cz>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Joonsoo Kim <iamjoonsoo.kim@....com>
Subject: Re: [PATCH v5 2/6] mm/cma: introduce new zone, ZONE_CMA
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> writes:
> ....
>
>> static inline void check_highest_zone(enum zone_type k)
>> {
>> - if (k > policy_zone && k != ZONE_MOVABLE)
>> + if (k > policy_zone && k != ZONE_MOVABLE && !is_zone_cma_idx(k))
>> policy_zone = k;
>> }
>>
>
>
> Should we apply policy to allocation from ZONE CMA ?. CMA reserve
> happens early and may mostly come from one node. Do we want the
> CMA allocation to fail if we use mbind(MPOL_BIND) with a node mask not
> including that node on which CMA is reserved, considering CMA memory is
> going to be used for special purpose.
Looking at this again, I guess CMA alloc is not going to depend on
memory policy, but this is for other movable allocation ?
-aneesh
Powered by blists - more mailing lists