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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9AB79C433EF for ; Wed, 16 Mar 2022 15:09:08 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id CC50D8D0001; Wed, 16 Mar 2022 11:09:07 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id C4C4A6B0072; Wed, 16 Mar 2022 11:09:07 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A50038D0001; Wed, 16 Mar 2022 11:09:07 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0173.hostedemail.com [216.40.44.173]) by kanga.kvack.org (Postfix) with ESMTP id 8F5436B0071 for ; Wed, 16 Mar 2022 11:09:07 -0400 (EDT) Received: from smtpin25.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 3DF55A0A17 for ; Wed, 16 Mar 2022 15:09:07 +0000 (UTC) X-FDA: 79250582334.25.44111A6 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf26.hostedemail.com (Postfix) with ESMTP id 5CA0B14000F for ; Wed, 16 Mar 2022 15:09:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1647443346; 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=q3DnrzNIWK5lpwiizhurtr0FleyyyipHQEpXQTzwkW4=; b=OrZIWuS7OrW5YXzYwGe7r897ZHBIZIrokAXDEffnHcAhPhO1zNCXvaJsXQ3sBFQ52VA67Y +dAd5EUCUc8qUIKJ69mHC2EYvQ8yJajUctSkh6KtHouRByAhYXlF47I8QRbkah4MR87gtg 4snVMTYjxjxj7/HxrSkhVyCOuksybR0= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-10-m3Jq1YHPN5ay5yQTupVdYA-1; Wed, 16 Mar 2022 11:09:04 -0400 X-MC-Unique: m3Jq1YHPN5ay5yQTupVdYA-1 Received: by mail-wr1-f69.google.com with SMTP id k20-20020adfc714000000b001e305cd1597so656265wrg.19 for ; Wed, 16 Mar 2022 08:09:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:organization:in-reply-to :content-transfer-encoding; bh=q3DnrzNIWK5lpwiizhurtr0FleyyyipHQEpXQTzwkW4=; b=3B4PJmkl/IdHhfvOt2aSDvIYynQ4MKNSgNBr6nz7q1lpN/rmdNuUWmdVzYi5Rm4f+d K3GofCr1CXWAUWUguF1phHgO+WN61LwUfbPIRCvXOXxcs/zm1W1rZ0VCCmKgAM1CCyiH 5CvqnCw4FeIUqDpsO9Zz0+cvM664ds7Wdz30Zvv/A1RITAlqwWDQbcVnz7IEHIO9RGnI e7mLDZmOvNSAbUtkgijssQeJCaImy3CVlSMk9Zt1A4iGSrOINm0SqBwwcstuxuIBNqH5 T4VdnMOpbq2UV/RvGK6jrM8qJ2Novy0EO5Uj0lkEXACRXkBBNzoB5W5gmgxHjqfIVnin +otQ== X-Gm-Message-State: AOAM532FcAf2FFCOO+SoCUHwuBGdm+UHR3Y//cPukWsBbGYBfknXRRjz 5h8p5BvHROjmEH65hAq20EvdUnpgBukvJOoybGm3aSeHC5HH3nTPkbjDqj33SF+3wljWP+jnW5U DbbT5/8F1jrc= X-Received: by 2002:a5d:4487:0:b0:1f1:232b:794f with SMTP id j7-20020a5d4487000000b001f1232b794fmr282047wrq.715.1647443343782; Wed, 16 Mar 2022 08:09:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwdGMAOtiEgH+F8EM8SK3ODiymGuIa/tjM0Wd/84EkJ4ZNTP9/YNOOhdV9pi6WwJFJAXQUx6g== X-Received: by 2002:a5d:4487:0:b0:1f1:232b:794f with SMTP id j7-20020a5d4487000000b001f1232b794fmr282025wrq.715.1647443343525; Wed, 16 Mar 2022 08:09:03 -0700 (PDT) Received: from ?IPV6:2003:cb:c706:f900:aa79:cd25:e0:32d1? (p200300cbc706f900aa79cd2500e032d1.dip0.t-ipconnect.de. [2003:cb:c706:f900:aa79:cd25:e0:32d1]) by smtp.gmail.com with ESMTPSA id z2-20020a056000110200b001e7140ddb44sm1849465wrw.49.2022.03.16.08.09.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 16 Mar 2022 08:09:03 -0700 (PDT) Message-ID: Date: Wed, 16 Mar 2022 16:09:02 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2 Subject: Re: [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support To: Xin Hao , sj@kernel.org Cc: rongwei.wang@linux.alibaba.com, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org References: From: David Hildenbrand Organization: Red Hat In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 5CA0B14000F X-Stat-Signature: og6yw54nwgwnxcopz769ngknruyuqmmk Authentication-Results: imf26.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=OrZIWuS7; dmarc=pass (policy=none) header.from=redhat.com; spf=none (imf26.hostedemail.com: domain of david@redhat.com has no SPF policy when checking 170.10.133.124) smtp.mailfrom=david@redhat.com X-Rspam-User: X-HE-Tag: 1647443346-456655 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 15.03.22 17:37, Xin Hao wrote: s/minotor/monitor/ > The purpose of these patches is to add CMA memory monitoring function. > In some memory tight scenarios, it will be a good choice to release more > memory by monitoring the CMA memory. I'm sorry, but it's hard to figure out what the target use case should be. Who will release CMA memory and how? Who will monitor that? What are the "some memory tight scenarios"? What's the overall design goal? -- Thanks, David / dhildenb