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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D25A1C433E0 for ; Wed, 6 Jan 2021 14:53:54 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 4084123110 for ; Wed, 6 Jan 2021 14:53:54 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4084123110 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 6FFA86B028C; Wed, 6 Jan 2021 09:53:53 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 6B0C26B028D; Wed, 6 Jan 2021 09:53:53 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 59E836B028E; Wed, 6 Jan 2021 09:53:53 -0500 (EST) 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 4253D6B028C for ; Wed, 6 Jan 2021 09:53:53 -0500 (EST) Received: from smtpin12.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 071DF8248076 for ; Wed, 6 Jan 2021 14:53:53 +0000 (UTC) X-FDA: 77675644746.12.hose54_4308c88274e2 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin12.hostedemail.com (Postfix) with ESMTP id D2535180555D0 for ; Wed, 6 Jan 2021 14:53:52 +0000 (UTC) X-HE-Tag: hose54_4308c88274e2 X-Filterd-Recvd-Size: 3078 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf32.hostedemail.com (Postfix) with ESMTP for ; Wed, 6 Jan 2021 14:53:52 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1609944830; 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=56aSTfmSA+spfUL4tlM8C1HuU4wDxeDMZKVuz0ExlJs=; b=rChqb3nnYyFTkjdLoJj6UCubjOGNjlXPq/sjyGZCn+pxXCN6AhYlepfsW7oVghGBNypjL9 GMrwKriJc2T1WF1AnIqnzLpgv4u+vpzUcIz58ugyMbYhrdfszF3AzNBHt4fQChqA0Ngt1S Thn/hj37EUxJjYaig+hOahL/OHluoX0= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id B9E1FADC4; Wed, 6 Jan 2021 14:53:50 +0000 (UTC) Date: Wed, 6 Jan 2021 15:53:49 +0100 From: Michal Hocko To: Shakeel Butt Cc: Johannes Weiner , Roman Gushchin , Yang Shi , Andrew Morton , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: memcg: add swapcache stat for memcg v2 Message-ID: <20210106145349.GN13207@dhcp22.suse.cz> References: <20210101023955.250965-1-shakeelb@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210101023955.250965-1-shakeelb@google.com> 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 Thu 31-12-20 18:39:55, Shakeel Butt wrote: > This patch adds swapcache stat for the cgroup v2. The swapcache > represents the memory that is accounted against both the memory and the > swap limit of the cgroup. The main motivation behind exposing the > swapcache stat is for enabling users to gracefully migrate from cgroup > v1's memsw counter to cgroup v2's memory and swap counters. > > Cgroup v1's memsw limit allows users to limit the memory+swap usage of a > workload but without control on the exact proportion of memory and swap. > Cgroup v2 provides separate limits for memory and swap which enables > more control on the exact usage of memory and swap individually for the > workload. > > With some little subtleties, the v1's memsw limit can be switched with > the sum of the v2's memory and swap limits. However the alternative for > memsw usage is not yet available in cgroup v2. Exposing per-cgroup > swapcache stat enables that alternative. Adding the memory usage and > swap usage and subtracting the swapcache will approximate the memsw > usage. This will help in the transparent migration of the workloads > depending on memsw usage and limit to v2' memory and swap counters. Could you expand a bit more on why memsw usage is important even in cgroup v2 land? How are you going to use the approximated value? I am not really objecting to adding this counter. We do export it for the global case and having a memcg view sounds useful for analysis. -- Michal Hocko SUSE Labs