Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp810230rwd; Thu, 15 Jun 2023 02:18:16 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6jr5lLQ0AA6S6W2b+sDiCqZFeGzCD5M/pr0NILUDhcPK3/UEYJov688e16Ew86J65DWGX5 X-Received: by 2002:a05:6359:29a:b0:129:c3a3:5efd with SMTP id ek26-20020a056359029a00b00129c3a35efdmr10165340rwb.24.1686820695987; Thu, 15 Jun 2023 02:18:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686820695; cv=none; d=google.com; s=arc-20160816; b=P1B0ZfH8BJ430gSSBMZEL12+3pIqwOr9DeKDFUJupJEPUQPYWgQOMMtXaM9y49FQPA 8bD63ih3eSMZbncmY7M7dHijhAizl40OkOlBt0XVERpdiF55N4DN9TBRhaooTtwNj6WL tIqz2DBpIprsN7pFMcqxb7Z7885KVye63RVESKHTDTAvKif86r1o+YDn0bW6Jr1HIHhX 7VJXz+t5Ptfdri7tEtBCevo06USvsZ/EkBQ7wLnDcQqCMJ/l43PbHJwyPYEclusZiRKr JT5k8C1phTQpgqb2Jr2dtmEX+xPu/YjMS7ndjE+YXe4gZeBTenIFJbLNwW8DW8UrGOKr Rx5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :organization:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:dkim-signature; bh=nuoYi2PVIfnh6Uy5UrMX0mBBCcoYRP6mjrxdUzD06aI=; b=XiCw8UEvIIP1tIdPA72jN2mR41GZjcMoY2KsNVuJ3KUxf4ndBT3SxjdS+mMp4SEZM7 uC4Z0HqynV0YRh26GhKPQsmO3+ZCA2wtnaXSXQb/HIzsvX9b0ilccqGVenhqibnbBnEy +kBzdbMUW8dKIFA6UzsU5kEfFaOXM0KIEaCMeD4/rNuXOOPQcIbPysNnrLM1nNnfvGQl pjic9MarY+BMzhHZBu+JAnXUuuVdTPInZXnIOGYw4XcEQWB4UZIoFBTmXUBe75LfLibK 4DDZ4zopJzv2Yhm35IF5WssRrvfn6DJY0he1mAcXvZDRPHSb9vgH3oXRnDsAgpyjkgGg lGCA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Sw64+ewQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 200-20020a6302d1000000b0054fd60530bfsi2918647pgc.590.2023.06.15.02.18.00; Thu, 15 Jun 2023 02:18:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Sw64+ewQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240867AbjFOInI (ORCPT + 99 others); Thu, 15 Jun 2023 04:43:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60994 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245193AbjFOImn (ORCPT ); Thu, 15 Jun 2023 04:42:43 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E33642135 for ; Thu, 15 Jun 2023 01:41:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1686818494; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nuoYi2PVIfnh6Uy5UrMX0mBBCcoYRP6mjrxdUzD06aI=; b=Sw64+ewQnCWGjAnkLeorgjslnZwgZGLGIfLK+ydH7eOArCTozfPAZAZHqiBORXPYSMzBKa kwnHnlT0935pNqB4a/LAyYNzXq1Psdt6ZXkFri58+tT78atAwXJMrJeJr3N7C17Nu6kRYH 1hn3CHSZrPuLPkq8J/lGmKGzdUrBFdg= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-669-HgNH5SMVM96Ipcy-AOZLcQ-1; Thu, 15 Jun 2023 04:41:32 -0400 X-MC-Unique: HgNH5SMVM96Ipcy-AOZLcQ-1 Received: by mail-wm1-f70.google.com with SMTP id 5b1f17b1804b1-3f7678c74beso10839175e9.3 for ; Thu, 15 Jun 2023 01:41:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686818492; x=1689410492; h=content-transfer-encoding:in-reply-to:organization:from:references :cc:to:content-language:subject:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nuoYi2PVIfnh6Uy5UrMX0mBBCcoYRP6mjrxdUzD06aI=; b=PbyMfVFFC2RsQ2AR5x3xiQ55nrZHt6RoCv6iujJEMOqyoP87ys1f4BlZnvD1saNHCm M+Ij2V+ZIZoMX+/X94ZxLBTlKWJzEYkHln+0zjDLenV8dJkRoQIMbGbCUvlax/t2UVsI tewqeQIIJq40p0gT6DpW+Lzlnwr6X1pgj3qX1pVeNNCcThVSdVMe08uzxcEuNSb2p0yS VUsDBo702V0RxQDy6fbg5lomfWVZ78f/RHDlb/lL8EaNpWSZwGmvs2n0GekSAKP/BPzE qD73lyt6YDlAmujh/a7C/NW34MvBem01NH4j7F2xrLmVoBl+SOYR9SIREEZoE0PjCLNF Xhkg== X-Gm-Message-State: AC+VfDyIMmoM17hSCyE9YQzfWt9jeauR+XExtNKPS7R+0G6nZRFtiIud N27VYaK898WvZ0mV4UfLHJq2DVNfHmU5mifemiCN/lJMhuNmWj2pexVKhT8O83SrjLpEhS4kVHq ByJviHvsnDxBdOdo8SAej30XQ X-Received: by 2002:a1c:f718:0:b0:3f7:7210:4f52 with SMTP id v24-20020a1cf718000000b003f772104f52mr12598371wmh.39.1686818491722; Thu, 15 Jun 2023 01:41:31 -0700 (PDT) X-Received: by 2002:a1c:f718:0:b0:3f7:7210:4f52 with SMTP id v24-20020a1cf718000000b003f772104f52mr12598359wmh.39.1686818491284; Thu, 15 Jun 2023 01:41:31 -0700 (PDT) Received: from ?IPV6:2a09:80c0:192:0:5dac:bf3d:c41:c3e7? ([2a09:80c0:192:0:5dac:bf3d:c41:c3e7]) by smtp.gmail.com with ESMTPSA id u26-20020a05600c211a00b003f42314832fsm19740769wml.18.2023.06.15.01.41.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 15 Jun 2023 01:41:30 -0700 (PDT) Message-ID: Date: Thu, 15 Jun 2023 10:41:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH v2] mm: compaction: skip memory hole rapidly when isolating migratable pages Content-Language: en-US To: "Huang, Ying" Cc: Baolin Wang , Mel Gorman , akpm@linux-foundation.org, vbabka@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <770f9f61472b24b6bc89adbd71a77d9cf62bb54f.1686646361.git.baolin.wang@linux.alibaba.com> <20230614095501.m4porztaibchrgwx@techsingularity.net> <87ilbpo1d9.fsf@yhuang6-desk2.ccr.corp.intel.com> <5f340d98-4ee0-35a9-58ed-943834d68042@linux.alibaba.com> <87fs6tfaw5.fsf@yhuang6-desk2.ccr.corp.intel.com> <5b5e7dd0-d60b-ca46-215c-f59947b805fe@redhat.com> <87bkhhf7d2.fsf@yhuang6-desk2.ccr.corp.intel.com> From: David Hildenbrand Organization: Red Hat In-Reply-To: <87bkhhf7d2.fsf@yhuang6-desk2.ccr.corp.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15.06.23 10:38, Huang, Ying wrote: > David Hildenbrand writes: > >> On 15.06.23 09:22, Huang, Ying wrote: >>> Baolin Wang writes: >>> >>>> On 6/15/2023 11:22 AM, Huang, Ying wrote: >>>>> Hi, Mel, >>>>> Mel Gorman writes: >>>>> >>>>>> On Tue, Jun 13, 2023 at 04:55:04PM +0800, Baolin Wang wrote: >>>>>>> On some machines, the normal zone can have a large memory hole like >>>>>>> below memory layout, and we can see the range from 0x100000000 to >>>>>>> 0x1800000000 is a hole. So when isolating some migratable pages, the >>>>>>> scanner can meet the hole and it will take more time to skip the large >>>>>>> hole. From my measurement, I can see the isolation scanner will take >>>>>>> 80us ~ 100us to skip the large hole [0x100000000 - 0x1800000000]. >>>>>>> >>>>>>> So adding a new helper to fast search next online memory section >>>>>>> to skip the large hole can help to find next suitable pageblock >>>>>>> efficiently. With this patch, I can see the large hole scanning only >>>>>>> takes < 1us. >>>>>>> >>>>>>> [ 0.000000] Zone ranges: >>>>>>> [ 0.000000] DMA [mem 0x0000000040000000-0x00000000ffffffff] >>>>>>> [ 0.000000] DMA32 empty >>>>>>> [ 0.000000] Normal [mem 0x0000000100000000-0x0000001fa7ffffff] >>>>>>> [ 0.000000] Movable zone start for each node >>>>>>> [ 0.000000] Early memory node ranges >>>>>>> [ 0.000000] node 0: [mem 0x0000000040000000-0x0000000fffffffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001800000000-0x0000001fa3c7ffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa3c80000-0x0000001fa3ffffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa4000000-0x0000001fa402ffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa4030000-0x0000001fa40effff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa40f0000-0x0000001fa73cffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa73d0000-0x0000001fa745ffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa7460000-0x0000001fa746ffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa7470000-0x0000001fa758ffff] >>>>>>> [ 0.000000] node 0: [mem 0x0000001fa7590000-0x0000001fa7ffffff] >>>>>>> >>>>>>> Signed-off-by: Baolin Wang >>>>>> >>>>>> This may only be necessary for non-contiguous zones so a check for >>>>>> zone_contiguous could be made but I suspect the saving, if any, would be >>>>>> marginal. >>>>>> >>>>>> However, it's subtle that block_end_pfn can end up in an arbirary location >>>>>> past the end of the zone or past cc->free_pfn. As the "continue" will update >>>>>> cc->migrate_pfn, that might lead to errors in the future. It would be a >>>>>> lot safer to pass in cc->free_pfn and do two things with the value. First, >>>>>> there is no point scanning for a valid online section past cc->free_pfn so >>>>>> terminating after cc->free_pfn may save some cycles. Second, cc->migrate_pfn >>>>>> does not end up with an arbitrary value which is a more defensive approach >>>>>> to any future programming errors. >>>>> I have thought about this before. Originally, I had thought that we >>>>> were safe because cc->free_pfn should be in a online section and >>>>> block_end_pfn should reach cc->free_pfn before the end of zone. But >>>>> after checking more code and thinking about it again, I found that the >>>>> underlying sections may go offline under us during compaction. So that, >>>>> cc->free_pfn may be in a offline section or after the end of zone. So, >>>>> you are right, we need to consider the range of block_end_pfn. >>>>> But, if we thought in this way (memory online/offline at any time), >>>>> it >>>>> appears that we need to check whether the underlying section was >>>>> offlined. For example, is it safe to use "pfn_to_page()" in >>>>> "isolate_migratepages_block()"? Is it possible for the underlying >>>>> section to be offlined under us? >>>> >>>> It is possible. There is a previous discussion[1] about the race >>>> between pfn_to_online_page() and memory offline. >>>> >>>> [1] >>>> https://lore.kernel.org/lkml/87zgc6buoq.fsf@nvidia.com/T/#m642d91bcc726437e1848b295bc57ce249c7ca399 >>> Thank you very much for sharing! That answers my questions >>> directly! >> >> I remember another discussion (but can't find it) regarding why memory >> compaction can get away without pfn_to_online_page() all over the >> place. The use is limited to __reset_isolation_pfn(). > > Per my understanding, isolate_migratepages() -> pageblock_pfn_to_page() > will check whether the pageblock is online. So if the pageblock isn't > offlined afterwards, we can use pfn_to_page(). Oh, indeed, that was the magic bit, thanks! -- Cheers, David / dhildenb