From: Prakash Gupta <guptap@codeaurora.org>
To: Joonsoo Kim <js1304@gmail.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Laura Abbott <labbott@redhat.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <guro@fb.com>, Minchan Kim <minchan@kernel.org>,
Rik van Riel <riel@surriel.com>,
Christian Koenig <christian.koenig@amd.com>,
Huang Rui <ray.huang@amd.com>,
Eric Biederman <ebiederm@xmission.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH 01/10] mm/page-flags: introduce PageHighMemZone()
Date: Wed, 10 Feb 2021 18:26:49 +0530 [thread overview]
Message-ID: <1b13af90-6e76-bde7-e861-5eb99c249e1d@codeaurora.org> (raw)
In-Reply-To: <CAAmzW4PUHw4utuS3tzMDFWqjDwUu14z8u=kxJa4wVEfEynFr1g@mail.gmail.com>
On 4/21/2020 12:13 PM, Joonsoo Kim wrote:
> This patchset is a preparation for my future patchset "mm/cma: manage the memory
> of the CMA area by using the ZONE_MOVABLE" [1] to solve the many CMA problems.
>
> CMA areas can be on the all the memory range, from ZONE_DMA to ZONE_HIGHMEM.
> And, in my future patchset [1], all the CMA areas are managed through
> the ZONE_MOVABLE
> and the range of the ZONE_MOVABLE is extended to cover all the CMA
> areas. In this
> case, following scenario would be possible.
>
> CMA area 1: 32MB size on the memory range 16MB~48MB (originally on the
> ZONE_NORMAL)
> CMA area 2: 32MB size on the memory range 896MB~928MB (originally on
> the ZONE_HIGHMEM)
>
> With my future patchset [1], ZONE_MOVABLE manages all the pages from
> CMA area 1 and 2.
> So, ZONE_MOVABLE has both direct mapped page and un-mapped page. Since one zone
> has two types of pages, current PageHighMem() implemented by using
> zone index could not
> work correctly. So, I make this patchset to change the PagHighMem()
> implementation.
Hello Joonsoo,
Resurrecting this thread. I wanted to check if you are still working on [1].
If yes, would you be posting it soon.
I think these would be useful for high CMA system.
Thanks,
Prakash
next prev parent reply other threads:[~2021-02-10 12:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:59 [PATCH 00/10] change the implemenation of the PageHighMem() js1304
2020-04-20 7:59 ` [PATCH 01/10] mm/page-flags: introduce PageHighMemZone() js1304
2020-04-20 11:20 ` Matthew Wilcox
2020-04-20 11:37 ` Vlastimil Babka
2020-04-21 6:43 ` Joonsoo Kim
2021-02-10 12:56 ` Prakash Gupta [this message]
2020-04-21 9:00 ` Christoph Hellwig
2020-04-22 1:02 ` Roman Gushchin
2020-04-22 7:42 ` Joonsoo Kim
2020-04-22 7:40 ` Joonsoo Kim
2020-04-20 7:59 ` [PATCH 02/10] drm/ttm: separate PageHighMem() and PageHighMemZone() use case js1304
2020-04-20 8:42 ` Christian König
2020-04-21 6:49 ` Joonsoo Kim
2020-04-20 7:59 ` [PATCH 03/10] mm/migrate: " js1304
2020-04-22 7:44 ` Christoph Hellwig
2020-04-22 7:55 ` Joonsoo Kim
2020-04-20 7:59 ` [PATCH 04/10] kexec: " js1304
2020-04-20 7:59 ` [PATCH 05/10] power: " js1304
2020-04-20 7:59 ` [PATCH 06/10] mm/gup: " js1304
2020-04-20 7:59 ` [PATCH 07/10] mm/hugetlb: " js1304
2020-04-20 7:59 ` [PATCH 08/10] mm: " js1304
2020-04-20 7:59 ` [PATCH 09/10] mm/page_alloc: correct the use of is_highmem_idx() js1304
2020-04-20 7:59 ` [PATCH 10/10] mm/page-flags: change the implementation of the PageHighMem() js1304
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=1b13af90-6e76-bde7-e861-5eb99c249e1d@codeaurora.org \
--to=guptap@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=christian.koenig@amd.com \
--cc=ebiederm@xmission.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=pavel@ucw.cz \
--cc=ray.huang@amd.com \
--cc=riel@surriel.com \
--cc=rjw@rjwysocki.net \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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 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).