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 2873FC4167B for ; Tue, 14 Nov 2023 09:56:20 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B6FF78D0038; Tue, 14 Nov 2023 04:56:19 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id B20608D002E; Tue, 14 Nov 2023 04:56:19 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A0F228D0038; Tue, 14 Nov 2023 04:56:19 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 910378D002E for ; Tue, 14 Nov 2023 04:56:19 -0500 (EST) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id 5EEF01209ED for ; Tue, 14 Nov 2023 09:56:19 +0000 (UTC) X-FDA: 81456104478.02.CD1C3F5 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by imf13.hostedemail.com (Postfix) with ESMTP id 5EE7020006 for ; Tue, 14 Nov 2023 09:56:16 +0000 (UTC) Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=hzCYTQBJ; spf=pass (imf13.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1699955776; h=from:from:sender: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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=GG7NCpHlhpgiMdgXsq8txfPY7HgpMI0ELvqXsyMN+B0=; b=P7tI262WLWya+0pChixx4bg4ql/E/z2opoWpfD2e18qu6oy8NbRuniQF9ECAQ5AKewF3HS MWnEwI1gcPhNRrDATnQCi8kePVLBLz7JN6BqQeyyefbsMd/N8IoNBmuMsCkIWbRDh0j5up jSFAQkhfY7LbisMMmrm8iEl3Il6Yfbk= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1699955776; a=rsa-sha256; cv=none; b=N5ydQZfX/wfTvhys2GJBo7dQqNzMewoZqEUhYS586xasHPJ0Ft7PUSH4iqV2m23eFE9Yev 65/HKlaE1GowG1JdmH6uZre/lFzHn6f4pzcN5KE9gDOn2M9FyBFU0BsBHN/N1aRdKguE/p +8ESgZICvYAXwhWX77sPhIuuCVIvWV8= ARC-Authentication-Results: i=1; imf13.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=hzCYTQBJ; spf=pass (imf13.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 676541F88C; Tue, 14 Nov 2023 09:56:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1699955774; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GG7NCpHlhpgiMdgXsq8txfPY7HgpMI0ELvqXsyMN+B0=; b=hzCYTQBJV6q9NahjU4QC8ODSVzO4KARfcX97NAUs4WT+dSDgRUqFx8rsLI30drDqNlZTdU jbH86i3mWSFr/g0leK9WamFVwbAVE5oXrRU8Ym4KrIqqFolONbutgSEZzXSMszmonbzd5b AHwy543zVn+4Ib+X9Afgd5Y8XFB8kWs= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4553C13416; Tue, 14 Nov 2023 09:56:14 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id sBznDT5EU2XaHgAAMHmgww (envelope-from ); Tue, 14 Nov 2023 09:56:14 +0000 Date: Tue, 14 Nov 2023 10:56:13 +0100 From: Michal Hocko To: Huan Yang Cc: "Huang, Ying" , Tejun Heo , Zefan Li , Johannes Weiner , Jonathan Corbet , Roman Gushchin , Shakeel Butt , Muchun Song , Andrew Morton , David Hildenbrand , Matthew Wilcox , Kefeng Wang , Peter Xu , "Vishal Moola (Oracle)" , Yosry Ahmed , Liu Shixin , Hugh Dickins , cgroups@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, opensource.kernel@vivo.com Subject: Re: [RFC 0/4] Introduce unbalance proactive reclaim Message-ID: References: <87edgufakm.fsf@yhuang6-desk2.ccr.corp.intel.com> <87a5rif58s.fsf@yhuang6-desk2.ccr.corp.intel.com> <97a3dbb3-9e73-4dcc-877d-f491ff47363b@vivo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Stat-Signature: bdcgrkyauofq5b7srcw575wfwegnpf96 X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 5EE7020006 X-Rspam-User: X-HE-Tag: 1699955776-12432 X-HE-Meta: U2FsdGVkX1/UaGWJuCiuveGZSmBP3KCxuJ/Et/5MxVddzs/7eLL3tLWCvGeeQ1z1snZ32k7mBmDWJ5+a8AZs8g8yBqXWVSfyWMwajAV70I9GBzS2Tz9sTi6Fye0YGK4VqfdP8C6FEb7OC2lf8uZ/on5/YoX4fK+Og1Ieo78lOYLzTEq+iURKek2vt2YQjaqdB+3Xx4+I14EwGjvikC3fshaOYBbO6KTiX/A+r2g9eH3xsbMrw3xV2WOFI+DQxjD3ddi9sPLuo2To2WKwcWdPpv+CNDmgWdTEWgbepOZZd9asMLiAAorEwjdQwI6Zz0Q5FWUy0RI8h57sNukjI7A90+ucs5nkshRpeJUNYcMpRkzK5k+uZ3TS8yT9QIfFos0Ncey6j1LeoCVdSNLBWRuT6dJKteeYeTaCN2/GGTyrqC7+JD3MxgTqbZJmbYYlbpsYQ1pkQuGUcyn+01fflGtHQS9u8vupUdykGPxtf1uXcWbnZh190T3A7etuxPxMIAfo8+rAPJbLACKh/kvBblxdSErPRRBaxSENe2JZ41ye55fTUjahIzfWoeesFI1fURckP7bCFtzg3fU7l/kmQwlHPNYQEZW4Q5SwFqVNFyg2SEU0OzHsUSkgIYfmaZXodSZx5TuQJ9GbNwB4TFyYTSz1pWgMcrsH8US9Qq7FFH2wpJxXNUQ7UM+6yJj4aIOSi5tZ3sz4XCqGALoJK/cE/d1NT5110bmdemqD246xwT7SH37nLf0Sitqx8uPU1UMtVTpuxOrR5ICaFh6K3zg37sw2Jrinu30+gyn/o2wAOGCyTYY3Q7rbu5hCwP4otMvcpcR+Sp6JptoHu071FFosl2qP7fMtJ5C6KzPTq2lx+wu1oFXagQlAcRFgiN1/JkMWClGkQ4SnyUmU98QkDLgLsEqKoQekUBBxtVe2hX6zL1VcLjY9hZsj+rIdJaSEVSes4fi+VIVDhn8L+Wu5fWG7VxJ H2ErD3lN e0LmwCOTQCppnQFmyaxMn/FX+AMz5ng5T7kVlCGqODEZiKvFKMZU5ZzC2xKrhDE/4ZxY2MYolQJYwCoaU/uqSwjegacCV+/VhP3lD5H6LLM/h9ED9uCD2f4wMCGcMJDW1eSiItMAC8w/GwJvSkMAmd0uvtUgWMm7/eAjBXqJCwjVabcirotLrNorK5he8E3xqNUkZYoEbyeHVScO+GtBHn9BEkzB0MnnvQCgi5Ig3xQMq80YPHauOj9RIbbFwHJPhuch2AoUNlzBqSjPcwzLdVDFvCakxTx+54VGpAGuzNjii9I7mdlcKdiEKXIsZCPK25iNs 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: List-Subscribe: List-Unsubscribe: On Tue 14-11-23 10:54:05, Michal Hocko wrote: > On Mon 13-11-23 16:26:00, Huan Yang wrote: > [...] > > However, considering that we need to perform proactive reclaim in batches, > > suppose that only 5% of the use-once page cache in this memcg can be > > reclaimed, > > but we need to call proactive memory reclaim step by step, such as 5%, 10%, > > 15% ... 100%. > > You haven't really explained this and I have asked several times IIRC. > Why do you even need to do those batches? Why cannot you simply relly on > the memory pressure triggering the memory reclaim? Do you have any > actual numbers showing that being pro-active results in smaller > latencies or anything that would show this is actually needed? Just noticed dcd2eff8-400b-4ade-a5b2-becfe26b437b@vivo.com, will reply there. -- Michal Hocko SUSE Labs