From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 94980EE49A8 for ; Sat, 19 Aug 2023 11:59:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232141AbjHSL7F (ORCPT ); Sat, 19 Aug 2023 07:59:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55336 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230289AbjHSL7D (ORCPT ); Sat, 19 Aug 2023 07:59:03 -0400 Received: from out30-113.freemail.mail.aliyun.com (out30-113.freemail.mail.aliyun.com [115.124.30.113]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 58F9E5B8F for ; Sat, 19 Aug 2023 04:58:55 -0700 (PDT) X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R201e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018046059;MF=baolin.wang@linux.alibaba.com;NM=1;PH=DS;RN=6;SR=0;TI=SMTPD_---0Vq5HBND_1692446330; Received: from 30.97.48.38(mailfrom:baolin.wang@linux.alibaba.com fp:SMTPD_---0Vq5HBND_1692446330) by smtp.aliyun-inc.com; Sat, 19 Aug 2023 19:58:51 +0800 Message-ID: Date: Sat, 19 Aug 2023 19:58:50 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Subject: Re: [PATCH 4/9] mm/compaction: simplify pfn iteration in isolate_freepages_range To: Kemeng Shi , linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, mgorman@techsingularity.net, david@redhat.com References: <20230805110711.2975149-1-shikemeng@huaweicloud.com> <20230805110711.2975149-5-shikemeng@huaweicloud.com> <43b726c1-3ea6-9acc-d4e4-c7deabcf7ecd@huaweicloud.com> <3729c50f-6f8e-2548-8932-f39045402299@linux.alibaba.com> <3574ed6e-34c8-47a1-8218-9e4cf1327184@huaweicloud.com> From: Baolin Wang In-Reply-To: <3574ed6e-34c8-47a1-8218-9e4cf1327184@huaweicloud.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/15/2023 6:37 PM, Kemeng Shi wrote: > > > on 8/15/2023 6:07 PM, Baolin Wang wrote: >> >> >> On 8/15/2023 5:32 PM, Kemeng Shi wrote: >>> >>> >>> on 8/15/2023 4:38 PM, Baolin Wang wrote: >>>> >>>> >>>> On 8/5/2023 7:07 PM, Kemeng Shi wrote: >>>>> We call isolate_freepages_block in strict mode, continuous pages in >>>>> pageblock will be isolated if isolate_freepages_block successed. >>>>> Then pfn + isolated will point to start of next pageblock to scan >>>>> no matter how many pageblocks are isolated in isolate_freepages_block. >>>>> Use pfn + isolated as start of next pageblock to scan to simplify the >>>>> iteration. >>>> >>>> IIUC, the isolate_freepages_block() can isolate high-order free pages, which means the pfn + isolated can be larger than the block_end_pfn. So in your patch, the 'block_start_pfn' and 'block_end_pfn' can be in different pageblocks, that will break pageblock_pfn_to_page(). >>>> >>> In for update statement, we always update block_start_pfn to pfn and >> >> I mean, you changed to: >> 1) pfn += isolated; >> 2) block_start_pfn = pfn; >> 3) block_end_pfn = pfn + pageblock_nr_pages; >> >> But in 1) pfn + isolated can go outside of the currnet pageblock if isolating a high-order page, for example, located in the middle of the next pageblock. So that the block_start_pfn can point to the middle of the next pageblock, not the start position. Meanwhile after 3), the block_end_pfn can point another pageblock. Or I missed something else? >> > Ah, I miss to explain this in changelog. > In case we could we have buddy page with order higher than pageblock: > 1. page in buddy page is aligned with it's order > 2. order of page is higher than pageblock order > Then page is aligned with pageblock order. So pfn of page and isolated pages > count are both aligned pageblock order. So pfn + isolated is pageblock order > aligned. That's not what I mean. pfn + isolated is not always pageblock-aligned, since the isolate_freepages_block() can isolated high-order free pages (for example: order-1, order-2 ...). Suppose the pageblock size is 2M, when isolating a pageblock (suppose the pfn range is 0 - 511 to make the arithmetic easy) by isolate_freepages_block(), and suppose pfn 0 to pfn 510 are all order-0 page, but pfn 511 is order-1 page, so you will isolate 513 pages from this pageblock, which will make 'pfn + isolated' not pageblock aligned. >>> update block_end_pfn to pfn + pageblock_nr_pages. So they should point >>> to the same pageblock. I guess you missed the change to update of >>> block_end_pfn. :) >>>>> >>>>> Signed-off-by: Kemeng Shi >>>>> --- >>>>>    mm/compaction.c | 14 ++------------ >>>>>    1 file changed, 2 insertions(+), 12 deletions(-) >>>>> >>>>> diff --git a/mm/compaction.c b/mm/compaction.c >>>>> index 684f6e6cd8bc..8d7d38073d30 100644 >>>>> --- a/mm/compaction.c >>>>> +++ b/mm/compaction.c >>>>> @@ -733,21 +733,11 @@ isolate_freepages_range(struct compact_control *cc, >>>>>        block_end_pfn = pageblock_end_pfn(pfn); >>>>>          for (; pfn < end_pfn; pfn += isolated, >>>>> -                block_start_pfn = block_end_pfn, >>>>> -                block_end_pfn += pageblock_nr_pages) { >>>>> +                block_start_pfn = pfn, >>>>> +                block_end_pfn = pfn + pageblock_nr_pages) { >>>>>            /* Protect pfn from changing by isolate_freepages_block */ >>>>>            unsigned long isolate_start_pfn = pfn; >>>>>    -        /* >>>>> -         * pfn could pass the block_end_pfn if isolated freepage >>>>> -         * is more than pageblock order. In this case, we adjust >>>>> -         * scanning range to right one. >>>>> -         */ >>>>> -        if (pfn >= block_end_pfn) { >>>>> -            block_start_pfn = pageblock_start_pfn(pfn); >>>>> -            block_end_pfn = pageblock_end_pfn(pfn); >>>>> -        } >>>>> - >>>>>            block_end_pfn = min(block_end_pfn, end_pfn); >>>>>              if (!pageblock_pfn_to_page(block_start_pfn, >>>> >>