From: Andrew Morton <akpm@linux-foundation.org>
To: js1304@gmail.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@lge.com, Vlastimil Babka <vbabka@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
Roman Gushchin <guro@fb.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Michal Hocko <mhocko@suse.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context
Date: Mon, 20 Jul 2020 16:16:13 -0700 [thread overview]
Message-ID: <20200720161613.15cddfdc2247377347f5471f@linux-foundation.org> (raw)
In-Reply-To: <1595220978-9890-1-git-send-email-iamjoonsoo.kim@lge.com>
On Mon, 20 Jul 2020 13:56:15 +0900 js1304@gmail.com wrote:
> Currently, preventing cma area in page allocation is implemented by using
> current_gfp_context(). However, there are two problems of this
> implementation.
>
> First, this doesn't work for allocation fastpath. In the fastpath,
> original gfp_mask is used since current_gfp_context() is introduced in
> order to control reclaim and it is on slowpath.
> Second, clearing __GFP_MOVABLE has a side effect to exclude the memory
> on the ZONE_MOVABLE for allocation target.
>
> To fix these problems, this patch changes the implementation to exclude
> cma area in page allocation. Main point of this change is using the
> alloc_flags. alloc_flags is mainly used to control allocation so it fits
> for excluding cma area in allocation.
What are the end user visible runtime effects of this change?
This is pretty much essential information when proposing a -stable
backport.
next prev parent reply other threads:[~2020-07-20 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 4:56 [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context js1304
2020-07-20 4:56 ` [PATCH v2 2/4] mm/gup: restrict CMA region by using allocation scope API js1304
2020-07-20 4:56 ` [PATCH v2 3/4] mm/hugetlb: make hugetlb migration callback CMA aware js1304
2020-07-20 4:56 ` [PATCH v2 4/4] mm/gup: use a standard migration target allocation callback js1304
2020-07-20 23:16 ` Andrew Morton [this message]
2020-07-20 23:23 ` [PATCH v2 1/4] mm/page_alloc: fix non cma alloc context Andrew Morton
2020-07-21 3:33 ` Joonsoo Kim
2020-07-21 3:33 ` Joonsoo Kim
2020-07-21 14:20 ` Sasha Levin
2020-07-23 1:53 ` Joonsoo Kim
2020-07-23 1:53 ` Joonsoo Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200720161613.15cddfdc2247377347f5471f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=guro@fb.com \
--cc=hch@infradead.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.