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;
MIME-Version: 1.0
References: <20201029200435.3386066-1-zi.yan@sent.com> <20201030094308.GG1478@dhcp22.suse.cz>
 <6CAAB1FC-2B41-490B-A67A-93063629C19B@nvidia.com> <20201030133625.GJ1478@dhcp22.suse.cz>
 <CAHbLzkqnmXqB-UThT9dMOwVpuweE6XwA78SF-_qD9=1EVpMSUg@mail.gmail.com> <BE903088-CF3E-4264-A9CA-8A27AC12EF65@nvidia.com>
In-Reply-To: <BE903088-CF3E-4264-A9CA-8A27AC12EF65@nvidia.com>
From:   Yang Shi <shy828301@gmail.com>
Date:   Fri, 30 Oct 2020 11:55:44 -0700
Message-ID: <CAHbLzkoSChyP4Jjz_LNxP3Maf-eVH0cfqRoN9=s75V0SMLEL-w@mail.gmail.com>
Subject: Re: [PATCH] mm/compaction: count pages and stop correctly during page isolation.
To:     Zi Yan <ziy@nvidia.com>
Cc:     Michal Hocko <mhocko@suse.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linux MM <linux-mm@kvack.org>, Rik van Riel <riel@surriel.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Vlastimil Babka <vbabka@suse.cz>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, Oct 30, 2020 at 11:39 AM Zi Yan <ziy@nvidia.com> wrote:
>
> On 30 Oct 2020, at 14:33, Yang Shi wrote:
>
> > On Fri, Oct 30, 2020 at 6:36 AM Michal Hocko <mhocko@suse.com> wrote:
> >>
> >> On Fri 30-10-20 08:20:50, Zi Yan wrote:
> >>> On 30 Oct 2020, at 5:43, Michal Hocko wrote:
> >>>
> >>>> [Cc Vlastimil]
> >>>>
> >>>> On Thu 29-10-20 16:04:35, Zi Yan wrote:
> >>>>> From: Zi Yan <ziy@nvidia.com>
> >>>>>
> >>>>> In isolate_migratepages_block, when cc->alloc_contig is true, we ar=
e
> >>>>> able to isolate compound pages, nr_migratepages and nr_isolated did=
 not
> >>>>> count compound pages correctly, causing us to isolate more pages th=
an we
> >>>>> thought. Use thp_nr_pages to count pages. Otherwise, we might be tr=
apped
> >>>>> in too_many_isolated while loop, since the actual isolated pages ca=
n go
> >>>>> up to COMPACT_CLUSTER_MAX*512=3D16384, where COMPACT_CLUSTER_MAX is=
 32,
> >>>>> since we stop isolation after cc->nr_migratepages reaches to
> >>>>> COMPACT_CLUSTER_MAX.
> >>>>>
> >>>>> In addition, after we fix the issue above, cc->nr_migratepages coul=
d
> >>>>> never be equal to COMPACT_CLUSTER_MAX if compound pages are isolate=
d,
> >>>>> thus page isolation could not stop as we intended. Change the isola=
tion
> >>>>> stop condition to >=3D.
> >>>>>
> >>>>> Signed-off-by: Zi Yan <ziy@nvidia.com>
> >>>>> ---
> >>>>>  mm/compaction.c | 8 ++++----
> >>>>>  1 file changed, 4 insertions(+), 4 deletions(-)
> >>>>>
> >>>>> diff --git a/mm/compaction.c b/mm/compaction.c
> >>>>> index ee1f8439369e..0683a4999581 100644
> >>>>> --- a/mm/compaction.c
> >>>>> +++ b/mm/compaction.c
> >>>>> @@ -1012,8 +1012,8 @@ isolate_migratepages_block(struct compact_con=
trol *cc, unsigned long low_pfn,
> >>>>>
> >>>>>  isolate_success:
> >>>>>            list_add(&page->lru, &cc->migratepages);
> >>>>> -          cc->nr_migratepages++;
> >>>>> -          nr_isolated++;
> >>>>> +          cc->nr_migratepages +=3D thp_nr_pages(page);
> >>>>> +          nr_isolated +=3D thp_nr_pages(page);
> >>>>
> >>>> Does thp_nr_pages work for __PageMovable pages?
> >>>
> >>> Yes. It is the same as compound_nr() but compiled
> >>> to 1 when THP is not enabled.
> >>
> >> I am sorry but I do not follow. First of all the implementation of the
> >> two is different and also I was asking about __PageMovable which shoul=
d
> >> never be THP IIRC. Can they be compound though?
> >
> > I have the same question, can they be compound? If they can be
> > compound, PageTransHuge() can't tell from THP and compound movable
> > page, right?
>
> Right. I have updated the patch and use compound_nr instead.

Thanks. Actually I'm wondering what kind of movable page could be
compound. Any real examples?

>
> =E2=80=94
> Best Regards,
> Yan Zi