Re: [PATCH v5 0/6] Introduce ZONE_CMA

From	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v5 0/6] Introduce ZONE_CMA
Date	2016-08-31 10:00 +0200
Message-ID	<sc8Bb-80v-5@gated-at.bofh.it> (permalink)
References	<sbmZz-36K-3@gated-at.bofh.it> <sbr3b-5vm-17@gated-at.bofh.it> <sbMAG-2mW-43@gated-at.bofh.it> <sbOCt-3C0-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Aug 30, 2016 at 04:09:37PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim <js1304@gmail.com> writes:
> 
> > 2016-08-29 18:27 GMT+09:00 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>:
> >> js1304@gmail.com writes:
> >>
> >>> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
> >>>
> >>> Hello,
> >>>
> >>> Changes from v4
> >>> o Rebase on next-20160825
> >>> o Add general fix patch for lowmem reserve
> >>> o Fix lowmem reserve ratio
> >>> o Fix zone span optimizaion per Vlastimil
> >>> o Fix pageset initialization
> >>> o Change invocation timing on cma_init_reserved_areas()
> >>
> >> I don't see much information regarding how we interleave between
> >> ZONE_CMA and other zones for movable allocation. Is that explained in
> >> any of the patch ? The fair zone allocator got removed by
> >> e6cbd7f2efb433d717af72aa8510a9db6f7a7e05
> >
> > Interleaving would not work since the fair zone allocator policy is removed.
> > I don't think that it's a big problem because it is just matter of
> > timing to fill
> > up the memory. Eventually, memory on ZONE_CMA will be fully used in
> > any case.
> 
> Does that mean a CMA allocation will now be slower because in most case we
> will need to reclaim ? The zone list will now have ZONE_CMA in the
> beginning right ?

ZONE_CMA will be used first but I don't think that CMA allocation will
be slower. In most case, memory would be fully used (usually
by page cache). So, we need reclaim or migration in any case.

Thanks.

Thread

[PATCH v5 0/6] Introduce ZONE_CMA js1304@gmail.com - 2016-08-29 07:10 +0200
  [PATCH v5 2/6] mm/cma: introduce new zone, ZONE_CMA js1304@gmail.com - 2016-08-29 07:10 +0200
    Re: [PATCH v5 2/6] mm/cma: introduce new zone, ZONE_CMA "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> - 2016-08-30 12:40 +0200
      Re: [PATCH v5 2/6] mm/cma: introduce new zone, ZONE_CMA "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> - 2016-08-30 14:50 +0200
        Re: [PATCH v5 2/6] mm/cma: introduce new zone, ZONE_CMA Joonsoo Kim <iamjoonsoo.kim@lge.com> - 2016-08-31 10:00 +0200
  [PATCH v5 3/6] mm/cma: populate ZONE_CMA js1304@gmail.com - 2016-08-29 07:10 +0200
  [PATCH v5 5/6] mm/cma: remove MIGRATE_CMA js1304@gmail.com - 2016-08-29 07:10 +0200
  [PATCH v5 6/6] mm/cma: remove per zone CMA stat js1304@gmail.com - 2016-08-29 07:10 +0200
  Re: [PATCH v5 0/6] Introduce ZONE_CMA "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> - 2016-08-29 11:30 +0200
    Re: [PATCH v5 0/6] Introduce ZONE_CMA Joonsoo Kim <js1304@gmail.com> - 2016-08-30 10:30 +0200
      Re: [PATCH v5 0/6] Introduce ZONE_CMA "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> - 2016-08-30 12:40 +0200
        Re: [PATCH v5 0/6] Introduce ZONE_CMA Joonsoo Kim <iamjoonsoo.kim@lge.com> - 2016-08-31 10:00 +0200
          Re: [PATCH v5 0/6] Introduce ZONE_CMA "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> - 2016-09-01 07:50 +0200
            Re: [PATCH v5 0/6] Introduce ZONE_CMA Joonsoo Kim <iamjoonsoo.kim@lge.com> - 2016-09-01 08:20 +0200

csiph-web