Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp7491502pxb; Thu, 18 Feb 2021 11:27:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJzmVzqQVB5iaYGjQNqdekFELcV/HubQR5I854MZrHWn5x4GQAPMuhCNS+KssNFAcwN+FQDr X-Received: by 2002:a05:6402:1c85:: with SMTP id cy5mr5632968edb.379.1613676420163; Thu, 18 Feb 2021 11:27:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613676420; cv=none; d=google.com; s=arc-20160816; b=NNLuU/oM5I5V+wfIIyzwvOjiMsiJgw6ATLCKCH/HwrOtL9s/ddScj1zOaOYU3yaTGI Zpy/qHcVFrn3QLWj8W/QH5OqG+O5/WKvBAAKo1VXwfkNvTkQ5S08VHwm8QLqaEaZbPTx aF9TFaUHGhF6OOrmyE+tfVqQmCww1Am6RkTdnQhG3a5GihyC8C0Lo5KGwwE2EBpehzX9 5n2mpi1S5th/opPWa6HG3MdNrY7SEz7Y3EApL2YWRf+4GRMoVPRrgXj5M4FIFfYOr1J+ 1PY/lj48faRvvJvN4Tcxcm47lkqjOWANfsdEDWVLKhctf6kyExxOcjHODUJvFTC1xb6r Fbrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :from:references:cc:to:subject:dkim-signature; bh=/532FGiDmXNyi77yaEvYqqbu5TAEWf0X1UPW7xyxBCc=; b=aHI/G9siMXasX4f9GjLKQAmJ5zpW/vt1PEZmzW2YBAC3iR3LL4aoNlrNKs+c8HHvYD mpR2tNxQ6boGcpWf/gAWmdrXvjNiSXS9w5MkU5+VduBDUhfNfqs7rP0vJFEW0DZao/Rw YMkb/KN4Ibeudp2r2SbbpqanYDykheEnNWSlTFB/Z9CyM6drPrACWH/3F16uAvlnXIq+ 0heHNFArQvIPJmK2eNjmKFDUB+vvJ1iw+GM5Cqw1cBCJsGDuiKzeYxBEh20pjaYKeKPQ DXclRrvPcOFvoIO12WFW1F/bYcEJyvo/L5VrJAnurx6oCDrOLlS/1k1UNvIZXeFVdyMM /QRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hlR7xbV2; 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=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g4si4203144edr.324.2021.02.18.11.26.36; Thu, 18 Feb 2021 11:27:00 -0800 (PST) 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=@redhat.com header.s=mimecast20190719 header.b=hlR7xbV2; 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=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232496AbhBRTXK (ORCPT + 99 others); Thu, 18 Feb 2021 14:23:10 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:53286 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232198AbhBRSSI (ORCPT ); Thu, 18 Feb 2021 13:18:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1613672199; 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=/532FGiDmXNyi77yaEvYqqbu5TAEWf0X1UPW7xyxBCc=; b=hlR7xbV24UmP9nVzbT17+n7WFWSwc1+FGHlSe3CDdhyS9oa/Hw5fyfDRpMDNdEjawxWRXL KYMJI6bIga92/9y5KdlxO2dQsDVfoiPwYXUiVNHQG+Sak7mHxiYSDNIDfIK88GG2KXYuZQ vRTxESZJMoggLQhDL83km2AmShWPaNI= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-314-p5q90FIUPO--_3QHzV_axQ-1; Thu, 18 Feb 2021 13:16:35 -0500 X-MC-Unique: p5q90FIUPO--_3QHzV_axQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id DC4921935780; Thu, 18 Feb 2021 18:16:33 +0000 (UTC) Received: from [10.36.114.59] (ovpn-114-59.ams2.redhat.com [10.36.114.59]) by smtp.corp.redhat.com (Postfix) with ESMTP id AECC360BE5; Thu, 18 Feb 2021 18:16:31 +0000 (UTC) Subject: Re: [PATCH RFC 0/1] mm: balancing the node zones occupancy To: Charan Teja Reddy , akpm@linux-foundation.org, rientjes@google.com, vbabka@suse.cz, mhocko@suse.com, mgorman@techsingularity.net, linux-mm@kvack.org Cc: vinmenon@codeaurora.org, sudaraja@codeaurora.org, linux-kernel@vger.kernel.org References: From: David Hildenbrand Organization: Red Hat GmbH Message-ID: <82e0e9c2-8187-8e2f-0d5e-304dafcda017@redhat.com> Date: Thu, 18 Feb 2021 19:16:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18.02.21 18:24, Charan Teja Reddy wrote: > I would like to start discussion about balancing the occupancy of > memory zones in a node in the system whose imabalance may be caused by > migration of pages to other zones during hotremove and then hotadding > same memory. In this case there is a lot of free memory in newly hotadd > memory which can be filled up by the previous migrated pages(as part of > offline/hotremove) thus may free up some pressure in other zones of the > node. Why is this specific to memory hot(un)plug? I think the problem is more generic: Assume 1. Application 1 allocates a lot of memory and gets ZONE_MOVABLE. 2. Application 2 allocates a lot of memory and gets ZONE_NORMAL. 3. Application 1 quits. Same problem, no? -- Thanks, David / dhildenb