From: Joonsoo Kim <firstname.lastname@example.org>
To: Andrew Morton <email@example.com>
Cc: Rik van Riel <firstname.lastname@example.org>,
Johannes Weiner <email@example.com>,
Laura Abbott <firstname.lastname@example.org>,
Minchan Kim <email@example.com>,
Marek Szyprowski <firstname.lastname@example.org>,
Michal Nazarewicz <email@example.com>,
"Aneesh Kumar K . V" <firstname.lastname@example.org>,
Vlastimil Babka <email@example.com>,
Russell King <firstname.lastname@example.org>,
Will Deacon <email@example.com>,
firstname.lastname@example.org, Tony Lindgren <email@example.com>,
Michal Hocko <firstname.lastname@example.org>
Subject: Re: [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE
Date: Fri, 22 Dec 2017 09:11:14 +0900 [thread overview]
Message-ID: <20171222001113.GA1729@js1304-P5Q-DELUXE> (raw)
On Fri, Dec 08, 2017 at 02:37:19PM -0800, Andrew Morton wrote:
> On Fri, 1 Dec 2017 16:53:03 +0900 email@example.com wrote:
> > From: Joonsoo Kim <firstname.lastname@example.org>
> > 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@atomide.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)" . 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?
Sorry for late response. I was on a long vacation.
I don't do anything on that patch yet. In fact, that patch isn't really
necessary to this patchset so I didn't include it into this patchset.
I will re-submit that patch after fixing the issue.
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to email@example.com. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"firstname.lastname@example.org"> email@example.com </a>
prev parent reply other threads:[~2017-12-22 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 7:53 [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE js1304
2017-12-01 7:53 ` [PATCH v2 1/3] " js1304
2017-12-01 7:53 ` [PATCH v2 2/3] mm/cma: remove ALLOC_CMA js1304
2017-12-01 7:53 ` [PATCH v2 3/3] ARM: CMA: avoid double mapping to the CMA area if CONFIG_HIGHMEM = y js1304
2017-12-05 16:48 ` [PATCH v2 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE Tony Lindgren
2017-12-08 22:37 ` Andrew Morton
2017-12-22 0:11 ` Joonsoo Kim [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).