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 4B17AC433EF for ; Thu, 17 Mar 2022 07:03:20 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8AC3F6B0071; Thu, 17 Mar 2022 03:03:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 85C478D0002; Thu, 17 Mar 2022 03:03:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 74AA58D0001; Thu, 17 Mar 2022 03:03:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.26]) by kanga.kvack.org (Postfix) with ESMTP id 65D5B6B0071 for ; Thu, 17 Mar 2022 03:03:19 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id 2E3AA22DFE for ; Thu, 17 Mar 2022 07:03:19 +0000 (UTC) X-FDA: 79252986918.11.AE65E65 Received: from out30-132.freemail.mail.aliyun.com (out30-132.freemail.mail.aliyun.com [115.124.30.132]) by imf05.hostedemail.com (Postfix) with ESMTP id 2D9FD100017 for ; Thu, 17 Mar 2022 07:03:16 +0000 (UTC) X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R101e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04395;MF=xhao@linux.alibaba.com;NM=1;PH=DS;RN=7;SR=0;TI=SMTPD_---0V7QLPIa_1647500592; Received: from B-X3VXMD6M-2058.local(mailfrom:xhao@linux.alibaba.com fp:SMTPD_---0V7QLPIa_1647500592) by smtp.aliyun-inc.com(127.0.0.1); Thu, 17 Mar 2022 15:03:13 +0800 From: Xin Hao Reply-To: xhao@linux.alibaba.com Subject: Re: [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support To: David Hildenbrand , sj@kernel.org Cc: rongwei.wang@linux.alibaba.com, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Baolin Wang References: Message-ID: <6e6ef9fa-3916-3449-954d-efd63a959019@linux.alibaba.com> Date: Thu, 17 Mar 2022 15:03:11 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 2D9FD100017 X-Rspam-User: Authentication-Results: imf05.hostedemail.com; dkim=none; dmarc=pass (policy=none) header.from=alibaba.com; spf=pass (imf05.hostedemail.com: domain of xhao@linux.alibaba.com designates 115.124.30.132 as permitted sender) smtp.mailfrom=xhao@linux.alibaba.com X-Stat-Signature: y98c6uiss8xm88yueh5hqcwcf7oy4jjx X-Rspamd-Server: rspam04 X-HE-Tag: 1647500596-926100 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: Hi David, On 3/16/22 11:09 PM, David Hildenbrand wrote: > On 15.03.22 17:37, Xin Hao wrote: > > s/minotor/monitor/ Thanks,  i will fix it. > >> 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? I may not be describing exactly what  i mean，My intention is to find out how much of the reserved CMA space is actually used and which is unused, For those that are not used, I understand that they can be released by cma_release(). Of course, This is just a little personal thought that I think is helpful for saving memory. > -- Best Regards! Xin Hao