From: "Christian König" <christian.koenig@amd.com>
To: js1304@gmail.com, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>,
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>, 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 02/10] drm/ttm: separate PageHighMem() and PageHighMemZone() use case
Date: Mon, 20 Apr 2020 10:42:13 +0200 [thread overview]
Message-ID: <412ea2bd-1719-c086-b3e7-64eec6e2bdc4@amd.com> (raw)
In-Reply-To: <1587369582-3882-3-git-send-email-iamjoonsoo.kim@lge.com>
Am 20.04.20 um 09:59 schrieb js1304@gmail.com:
> From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
> Until now, PageHighMem() is used for two different cases. One is to check
> if there is a direct mapping for this page or not. The other is to check
> the zone of this page, that is, weather it is the highmem type zone or not.
>
> Now, we have separate functions, PageHighMem() and PageHighMemZone() for
> each cases. Use appropriate one.
>
> Note that there are some rules to determine the proper macro.
>
> 1. If PageHighMem() is called for checking if the direct mapping exists
> or not, use PageHighMem().
> 2. If PageHighMem() is used to predict the previous gfp_flags for
> this page, use PageHighMemZone(). The zone of the page is related to
> the gfp_flags.
> 3. If purpose of calling PageHighMem() is to count highmem page and
> to interact with the system by using this count, use PageHighMemZone().
> This counter is usually used to calculate the available memory for an
> kernel allocation and pages on the highmem zone cannot be available
> for an kernel allocation.
> 4. Otherwise, use PageHighMemZone(). It's safe since it's implementation
> is just copy of the previous PageHighMem() implementation and won't
> be changed.
>
> I apply the rule #4 for this patch.
>
> Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Reviewed-by: Christian König <christian.koenig@amd.com> for the TTM
changes, but I can't judge if the general approach makes sense or not.
Regards,
Christian.
> ---
> drivers/gpu/drm/ttm/ttm_memory.c | 4 ++--
> drivers/gpu/drm/ttm/ttm_page_alloc.c | 2 +-
> drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 2 +-
> drivers/gpu/drm/ttm/ttm_tt.c | 2 +-
> 4 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_memory.c b/drivers/gpu/drm/ttm/ttm_memory.c
> index acd63b7..d071b71 100644
> --- a/drivers/gpu/drm/ttm/ttm_memory.c
> +++ b/drivers/gpu/drm/ttm/ttm_memory.c
> @@ -641,7 +641,7 @@ int ttm_mem_global_alloc_page(struct ttm_mem_global *glob,
> */
>
> #ifdef CONFIG_HIGHMEM
> - if (PageHighMem(page) && glob->zone_highmem != NULL)
> + if (PageHighMemZone(page) && glob->zone_highmem != NULL)
> zone = glob->zone_highmem;
> #else
> if (glob->zone_dma32 && page_to_pfn(page) > 0x00100000UL)
> @@ -656,7 +656,7 @@ void ttm_mem_global_free_page(struct ttm_mem_global *glob, struct page *page,
> struct ttm_mem_zone *zone = NULL;
>
> #ifdef CONFIG_HIGHMEM
> - if (PageHighMem(page) && glob->zone_highmem != NULL)
> + if (PageHighMemZone(page) && glob->zone_highmem != NULL)
> zone = glob->zone_highmem;
> #else
> if (glob->zone_dma32 && page_to_pfn(page) > 0x00100000UL)
> diff --git a/drivers/gpu/drm/ttm/ttm_page_alloc.c b/drivers/gpu/drm/ttm/ttm_page_alloc.c
> index b40a467..847fabe 100644
> --- a/drivers/gpu/drm/ttm/ttm_page_alloc.c
> +++ b/drivers/gpu/drm/ttm/ttm_page_alloc.c
> @@ -530,7 +530,7 @@ static int ttm_alloc_new_pages(struct list_head *pages, gfp_t gfp_flags,
> /* gfp flags of highmem page should never be dma32 so we
> * we should be fine in such case
> */
> - if (PageHighMem(p))
> + if (PageHighMemZone(p))
> continue;
>
> #endif
> diff --git a/drivers/gpu/drm/ttm/ttm_page_alloc_dma.c b/drivers/gpu/drm/ttm/ttm_page_alloc_dma.c
> index faefaae..338b2a2 100644
> --- a/drivers/gpu/drm/ttm/ttm_page_alloc_dma.c
> +++ b/drivers/gpu/drm/ttm/ttm_page_alloc_dma.c
> @@ -747,7 +747,7 @@ static int ttm_dma_pool_alloc_new_pages(struct dma_pool *pool,
> /* gfp flags of highmem page should never be dma32 so we
> * we should be fine in such case
> */
> - if (PageHighMem(p))
> + if (PageHighMemZone(p))
> continue;
> #endif
>
> diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
> index 2ec448e..6e094dd 100644
> --- a/drivers/gpu/drm/ttm/ttm_tt.c
> +++ b/drivers/gpu/drm/ttm/ttm_tt.c
> @@ -119,7 +119,7 @@ static int ttm_tt_set_page_caching(struct page *p,
> {
> int ret = 0;
>
> - if (PageHighMem(p))
> + if (PageHighMemZone(p))
> return 0;
>
> if (c_old != tt_cached) {
next prev parent reply other threads:[~2020-04-20 8:42 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
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 [this message]
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=412ea2bd-1719-c086-b3e7-64eec6e2bdc4@amd.com \
--to=christian.koenig@amd.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.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 \
/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).