Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3208102ybz; Sun, 3 May 2020 20:35:29 -0700 (PDT) X-Google-Smtp-Source: APiQypJ1AZuZnkaeegIWmEk/JuX5j035EMnZkn03AnaMGRzPR1E+DxSKm4WfY8W0/xcikOdjKNXf X-Received: by 2002:a17:906:8282:: with SMTP id h2mr13760183ejx.250.1588563329277; Sun, 03 May 2020 20:35:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588563329; cv=none; d=google.com; s=arc-20160816; b=p73N/uRIOBuEu7sLZlF1L8M7IGrT+HI+i8H1cVhzw7LTpO3NleAKSqERsnWSb8luc/ MGMJ6lQx+U0RFgc1fKqjBAHuLjURUW4VMbe/WpaFzhQNagVJYxLEWs2miPFhCTEQ9YVj QUT85nPIvamHrgwc0VPj0JU/Jh94lu/gZH4RUfwTmfeDHYikQfjI5y/MTFJnjM37dz4w 4KYdfBOcCUKhXSsFoH2jFgVKvr0ZYfuE3fFopvUCcLE6hfL2AbcziHqTG42ZkbLvs9KB 1bVaGVWj1QPvuukoDKewWwZylEPcivTmEM2N/fY6aTTaeeuj/k4ZEJorjkVK5IZytnm5 /c1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=IjhzQ3oHa9nNeIuiLupnxo7YU2u+0fWxdlUhWitx3YU=; b=K6Vg6ZbZYnX0Ob78FqXe2DS+IBo3RnVHIBnD9DIPonkZCxipcpghmniRiz9shIqGyf Vva1zaWK1m/tyZrTvy+cgYA4cktA71WXSeap+uV3se2qJiGNN5FiKRIXsF6nad+WBhG0 brzGpmsiN9JQE3VdfVVf8Lgoc7DLvJSpiXTwLQ3wJnoKkvQmr24YU44/chrM0iSjU3eE RevAWj2RFr3kvJcTvz0pzAtHHlpoV7kepDqx5H2neN9/OE5JqatkZRRboEbC0GEAwjII O4rbQj5zGbOtUpF7s/BATiAy8o6gkzU5cwWZ5CiJMwqZLmJ7gZXxt5r68FvkbZaq27Do 5UHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=VY0BX8QJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h20si6509202eds.141.2020.05.03.20.35.06; Sun, 03 May 2020 20:35:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=VY0BX8QJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727123AbgEDDJX (ORCPT + 99 others); Sun, 3 May 2020 23:09:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59402 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726768AbgEDDJX (ORCPT ); Sun, 3 May 2020 23:09:23 -0400 Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DA0E4C061A0E for ; Sun, 3 May 2020 20:09:22 -0700 (PDT) Received: by mail-qv1-xf2e.google.com with SMTP id v18so7697387qvx.9 for ; Sun, 03 May 2020 20:09:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=IjhzQ3oHa9nNeIuiLupnxo7YU2u+0fWxdlUhWitx3YU=; b=VY0BX8QJL/Ls8mKkxdOnZWoc/16ZP/mvIQfcoHIcj1h/K2Q2zQh4jUPwqUTBdL0/gf B/V3IiNsa7a7TQFt2egmpLSRf7jrnXzSaQhRP4vAamVcc+66FrZSPEWYVrbYuzcEC126 damw8M1AurzoePG5McVEwdfx+HHJ78R3X9+vqJUwrzBP8PW0VmM2UDFvA0LhACCwFWa5 ZENGXzZ+BPVX7AgJElbGuJdcFA3A8KksJ9U8cDmfCbVNyEBLTxim+YNdRHfgkjJFHz+Q rCyOz/nrabbolc5/vqm39RXSn6Yy3h00G+9J0rJ0pter4I7xyDYZ0RNdDJM8oMXAF9Bg Wa0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=IjhzQ3oHa9nNeIuiLupnxo7YU2u+0fWxdlUhWitx3YU=; b=Qg4Gcs3QVyC3wEJnQNa5Kaij9jZoSSARr/VnouOvUA/4f5qdUkT59YaR2GHnsM+FTB 1iO5/161r8CUMvyPGc3R+WL7/k1R+NJjh0GTGQP/5xN1D7imPeoxL3v4xBsSCRZNmNnZ vPHEWVQ22Hujtwnc8YNCh/8jZ65Ij7T+7dPFCnFu6u9uSGRQ3GoAtrfanrXBIvJQwJT6 iN01Ci5hfGxkk1vuHYIz1q0z0jUGMXw3ADu3Q0P7XT4VVMiBDjA673KEHXOO0GQJ5gh1 B0gVCZU+8IDZbqkISxGeJJdfRo2D9QBGKGOUy/rmB26aTf7Hf9Ao75Yh3U7lWpZZ/HFn rvwg== X-Gm-Message-State: AGi0Puavg8FqKXGfQ1Mqx0fxV3OIcczQYGuKNyHhf4hWQs7X+fgePB40 YDxI/IapD4gBeZbIE5s8CIVb9asuKXnRHC/9n/g= X-Received: by 2002:a05:6214:7e1:: with SMTP id bp1mr14347599qvb.208.1588561762103; Sun, 03 May 2020 20:09:22 -0700 (PDT) MIME-Version: 1.0 References: <1588130803-20527-1-git-send-email-iamjoonsoo.kim@lge.com> <20200429184711.9d603da097fdea80f574f1f1@linux-foundation.org> <20200501105545.GA29460@infradead.org> <20200501123429.GA26861@infradead.org> In-Reply-To: <20200501123429.GA26861@infradead.org> From: Joonsoo Kim Date: Mon, 4 May 2020 12:09:11 +0900 Message-ID: Subject: Re: [PATCH v2 00/10] change the implementation of the PageHighMem() To: Christoph Hellwig Cc: Andrew Morton , Linux Memory Management List , LKML , Vlastimil Babka , Laura Abbott , "Aneesh Kumar K . V" , Mel Gorman , Michal Hocko , Johannes Weiner , Roman Gushchin , Minchan Kim , Rik van Riel , Christian Koenig , Huang Rui , Eric Biederman , "Rafael J . Wysocki" , Pavel Machek , kernel-team@lge.com, Joonsoo Kim Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2020=EB=85=84 5=EC=9B=94 1=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 9:34, Ch= ristoph Hellwig =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1: > > On Fri, May 01, 2020 at 09:15:30PM +0900, Joonsoo Kim wrote: > > I think that PageHighMemZone() is long and complicated enough to have > > a macro. > > It is. But then again it also shouldn't really be used by anything > but MM internals. I'm not sure that we can make it MM internal but I will try. > > > > PageHighMemZone(page) =3D is_highmem_idx(zone_idx(page_zone(page)) > > > > Instead of open-code, how about changing the style of macro like as > > page_from_highmem()? What PageHighMemZone() represent is derivated > > attribute from the page so PageXXX() style may not be appropriate. > > Maybe page_is_highmem_zone() with a big kerneldoc comment explaining > the use case? Bonus points of killing enough users that it can be > in mm/internal.h. I will try to kill page_is_highmem_zone() as much as possible in next versi= on. Thanks.