Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37;
MIME-Version: 1.0
References: <1683782550-25799-1-git-send-email-zhaoyang.huang@unisoc.com>
 <20231006141750.5423083520f74bc0746fd249@linux-foundation.org>
 <CAGWkznHqQHMN1QXz7os7AQTYdzc3+LEq+z2bWOzLbiseV=560A@mail.gmail.com>
 <20231009171415.cfc26b45c2f9f4489afe16c2@linux-foundation.org> <ZSSpfw_VdFkus4F5@P9FQF9L96D>
In-Reply-To: <ZSSpfw_VdFkus4F5@P9FQF9L96D>
From:   Zhaoyang Huang <huangzhaoyang@gmail.com>
Date:   Tue, 10 Oct 2023 09:42:36 +0800
Message-ID: <CAGWkznG+-j8WqM6wSf5yaSi7qZzyb0SbkbOH1Cwq7WaQ1-6RGA@mail.gmail.com>
Subject: Re: [PATCHv5] mm: optimization on page allocation when CMA enabled
To:     Roman Gushchin <roman.gushchin@linux.dev>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        "zhaoyang.huang" <zhaoyang.huang@unisoc.com>,
        Roman Gushchin <guro@fb.com>, Minchan Kim <minchan@kernel.org>,
        Joonsoo Kim <iamjoonsoo.kim@lge.com>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, ke.wang@unisoc.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Oct 10, 2023 at 9:31=E2=80=AFAM Roman Gushchin <roman.gushchin@linu=
x.dev> wrote:
>
> On Mon, Oct 09, 2023 at 05:14:15PM -0700, Andrew Morton wrote:
> > On Sun, 8 Oct 2023 15:54:40 +0800 Zhaoyang Huang <huangzhaoyang@gmail.c=
om> wrote:
> >
> > > > Roman previously asked
> > > >
> > > > : Also I'm a bit concerned about potential performance implications=
.
> > > > : Would be great to provide some benchmarks or some data.  Probably=
 it's
> > > > : ok because of we have pcp caches on top, but I'm not 100% sure.
> > > >
> > > > Are you able to perform such testing and tell us the result?
> > > I have applied this patch in a v5.4 based ANDROID system and got no
> > > regression problem. Actually, this commit is aimed to have
> > > alloc_pages(GFP_USER) use CMA instead of stealing U&R(could lead to
> > > GFP_KERNEL fail) only when zone's free pages and free cma are around
> > > WATERMARK_LOW/MIN which would NOT affect most scenarios.
> >
> > OK, thanks.
> >
> > Could the appropriate people please take a look at this?  It has been
> > in mm-unstable since May.
>
> I have 2 concerns:
> 1) it's still hard to understand the commit message and comments, I can
>    only reverse-engineer it based on the code changes;
> 2) performance concerns I expressed earlier are not addressed. Idk what's
>    a good benchmark for the page allocator, probably something i/o or
>    networking heavy.
>
ok, I will update the commit message

> On the positive side I believe that the patch is solving a real problem.