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 05ACFC3600C for ; Thu, 3 Apr 2025 09:17:00 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 62C06280005; Thu, 3 Apr 2025 05:16:59 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5DABA280001; Thu, 3 Apr 2025 05:16:59 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4A20E280005; Thu, 3 Apr 2025 05:16:59 -0400 (EDT) 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 2C31B280001 for ; Thu, 3 Apr 2025 05:16:59 -0400 (EDT) Received: from smtpin30.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id CD9DC141B81 for ; Thu, 3 Apr 2025 09:16:59 +0000 (UTC) X-FDA: 83292178158.30.DAFE895 Received: from mail-pj1-f41.google.com (mail-pj1-f41.google.com [209.85.216.41]) by imf08.hostedemail.com (Postfix) with ESMTP id E98D8160017 for ; Thu, 3 Apr 2025 09:16:57 +0000 (UTC) Authentication-Results: imf08.hostedemail.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=S3jFZ7OS; spf=pass (imf08.hostedemail.com: domain of jingxiangzeng.cas@gmail.com designates 209.85.216.41 as permitted sender) smtp.mailfrom=jingxiangzeng.cas@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1743671818; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=sl4RKGtIF3Wx8smkosZ2Z9mqMxRoYVSserc8AMAHE/I=; b=uvvvwGzle/fUnHX6FjlbzNPBlJ4eRd3cMMow4Ca+1VfvpAk/x+xxGA00vTYa25s3LdslKV 9i5aN5p/TbIqg2hotV34Ko3TjIqQnV7gSzmPNWxATenoNg5LRtqDhOCTfI49CaRRoTEsG3 4mXu+8IlZ7DIKfbKC7/0Q2clE6/eyFY= ARC-Authentication-Results: i=1; imf08.hostedemail.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=S3jFZ7OS; spf=pass (imf08.hostedemail.com: domain of jingxiangzeng.cas@gmail.com designates 209.85.216.41 as permitted sender) smtp.mailfrom=jingxiangzeng.cas@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1743671818; a=rsa-sha256; cv=none; b=j/drTeswIVGnxKAJDu5g91mbDw5ZbO2eB8kXQWplBCiSRHmfDwMWldj3DzyHs3TadfGM1B BTA4uh2cMk43joB8xwndsjRUKrJ6GHx7eWK8MEYknBfHWczrgpVQLyLuTXRUrJtZ4qNXkT UkJujUXVL6o8hTEunX5Mh+6UsCsbEKk= Received: by mail-pj1-f41.google.com with SMTP id 98e67ed59e1d1-30185d00446so539228a91.0 for ; Thu, 03 Apr 2025 02:16:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1743671817; x=1744276617; darn=kvack.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=sl4RKGtIF3Wx8smkosZ2Z9mqMxRoYVSserc8AMAHE/I=; b=S3jFZ7OSiPpqu7Q3X2zUqbYNrzBIFQr6BRRHqs9mVsk+R5zzC5KeHhW3kuTDmnxKr8 iYfcBJe6IVh7XC1gqJeR144zahzsXAL5dbxyej3Cr8DhFqlCDQTZxo4ZVlr/oX0/6wpC M5dJhvWtGByBvQjHMQbj4XOGM4KU60OVIM8JEgTvDrtWtYab0H0+ubJKutkdG8lLZ/S2 67zzbQ8uMYzV9QGyZReKnhAOEQb0ukbvev50QGl74EQuesnKXilhDpuL6BJ08lxdB2y3 NqjHcSHw+wvcKx/MegWyGHLlC7X820bF9F05Cq6NgVFL/1zWkt1VmcCE3CdViUqDm9tj 3RWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743671817; x=1744276617; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=sl4RKGtIF3Wx8smkosZ2Z9mqMxRoYVSserc8AMAHE/I=; b=WWDKJWfqAtrvdubxOjWSEhBwhMfUtaxofYhHIA+9z74eNG7MJz9N/3vpbPjBnslNB3 TLovjp8l+DLKSIL6GD9UPXWH4rTJI26MaM1bFOtdmPrXV2+96I01xNKlyTU1qy50sDku 0GxgHAG/o5xKUFYC7eDIitIgjzVz9dec4hclQtGd2q77Y2kf0P0mY4iowJ5TvXw/kKyp Ab7TxasMa/uAAptmRn377YOUO314K/CaFHIPNe9cig4PFN617mdofBqugHwAZUs8xIkL E1shv5qBZ+pKKLZNkN7mOQN0xzOfOfZrWHWshxW6VT9z4sIuelVZgb3+56RzR9aHEYMb tSNA== X-Forwarded-Encrypted: i=1; AJvYcCXlRqof205M1u7laFhHY9r6bVzNUo/OkC423p691/jupx/+Y4QbgppEhFmsznn4hJpYgiFzwG/lFw==@kvack.org X-Gm-Message-State: AOJu0YzbiSfmV01UMIRy0PDNoR59jKKkR4NpIolxVZYOUzqUzJKpXEJu Yh0Sf8UwiIpIn7kDD9Z2HZsgNx4OQY1CXdTWxlx3LT8kRhTEcj8q2dp5F8VeFWq7SxDubbC34BQ ggjgtSiZcQ1aT40rEdywA+K6bgCg= X-Gm-Gg: ASbGncsyClsd0cABXagf+KdTFGp91sppnrmiFtThc9KDXe6b9zB+bvYdBIqxZK9pXjC RxRMijPuqtFpoCcTPBKM9OiMMEXzXYZkPcCCnS/13Q36J8HuVFyoOtXt3FQ3GkBqMDvmNsjwNVd hn8g5QZ8twZucJi1ocDnQ54HtmLA== X-Google-Smtp-Source: AGHT+IHW3xtLpmtp+xLHdFxtdp1Io+v/9JTxu9DwE0nf+jF7/zRfoCM4JVQSGsMmAW+XG4LYtfDNfSFt0Mo0wX+8quw= X-Received: by 2002:a17:90a:f944:b0:2fe:b907:5e5a with SMTP id 98e67ed59e1d1-3057a5ebbb1mr3748649a91.10.1743671816572; Thu, 03 Apr 2025 02:16:56 -0700 (PDT) MIME-Version: 1.0 References: <20250319064148.774406-1-jingxiangzeng.cas@gmail.com> <20250319064148.774406-3-jingxiangzeng.cas@gmail.com> <7ia4tt7ovekj.fsf@castle.c.googlers.com> <20250320142846.GG1876369@cmpxchg.org> <4lygax4lgpkkmtmpxif6psl7broial2h74lel37faelc3dlsx3@s56hfvqiazgc> In-Reply-To: From: jingxiang zeng Date: Thu, 3 Apr 2025 17:16:45 +0800 X-Gm-Features: AQ5f1Jq4gJ4BRiU4bC5rIWpMztSzrk2KsAJ8ThKe-zAr_EtKDSxBPe0BrSwDPHA Message-ID: Subject: Re: [External] Re: [RFC 2/5] memcontrol: add boot option to enable memsw account on dfl To: Zhongkun He Cc: =?UTF-8?Q?Michal_Koutn=C3=BD?= , Shakeel Butt , Johannes Weiner , Roman Gushchin , Jingxiang Zeng , akpm@linux-foundation.org, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, mhocko@kernel.org, muchun.song@linux.dev, kasong@tencent.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: E98D8160017 X-Rspam-User: X-Rspamd-Server: rspam02 X-Stat-Signature: be1a1dpgz3nk1w3ktpytittn6w3nnnth X-HE-Tag: 1743671817-93175 X-HE-Meta: U2FsdGVkX1/c1Zs441O43TJfOBXoLE29W14YkiCGgl+6QqzCAZP1Msserjl/q2gI6YG2iOa5VOOKn5X0XO6zWUyyjU3P89a8eiVqXJoSmFCbE4oL+bnDK8hce3sb+ZVp+gSaamq3DBJbfQikk79B/U6qLryLzMiHSgVIP7+LU4gIF91sSxSpXWhSWnMC74x6j44KQDCE0DdvMqNdSyCHyTkKeZF+WdhKJgo1MDWnkdBo/7nWjzx5S2Bzt38iIrxbVxpTfDJn18EaGmO7vCuPu0lUiWY+aPLOXeiBGHtrIvxFTmP/n/EW/h44lxZthS/8nW3XRaY+Vzx/xegtNz1AUK+8gvcslatcSJgnBje0AON7IkN5hEfxKCRNpRkOWkSjshGLPKWYaeJXXLz+Vql4uIfNkbvEG54XeLOCo82wyjJ55X//0Z3ENYOFRRHzZOzUY9oQe/yHU84cPvZverxqrW21PIP8I+R/9NCDKcNnzZ00xyBEvGYl9DxvBmScW5VumxQcusU15FU8wXIUguzzGfI3R1gJ6BV9iSGgg3203ZAs54WjY4Tr1mgA1Pfz8nuuzZuL9PZIctMvRg0luo9oh32tMC36aoh1mFj7mHXLlfJ7Fs2RPIc/q7WXC+2nV1xF5FLu7kG7baPRLevV07mJSdvVwZ9Dy22Bl4DjQ7REpBeYoB1ARBKKlfKAbonLGOx117FJ/Q9RH3DhVaJucZYdxF/uqwvh9j3pvDW+rcgrOkmF5h+BsFxScWEjZBMzVJ/7lLR1oQWmKVxuhn7bTCZO1af7hGcI1BCtoEUkGCaPdAF8DSNFMuoL3CbAhGyXfnJ52MBhVyDKpChqYRL3/Wgiqlcswc/X1iKA5Se1lxPaQuRBoeKgmGSttcT+04bI8ZHcM7IRPvdnL5b9e2nxC6/KrcDwLU5wFXHbtB28hZLFjmf76be+E4bkq4CP/+9peH0xqr46q7PUISmmniVSJT3 i5Gy+aJo 3UCiLPSSCekd2mB8OI99MpSL13ug3eCwxpsSh7sH+vErXRTQC+bInKc3KYTLxNrhlld25IgbRg8CvZaD5NBASMxJsAmmUsbw+Rf6zFQvWW/JUEo5OI7U+/RN3qQYYQ1dzaDVplKtMZ5w/GmPDvg+9nd5xF0fKv4dfRKEu3TNS4VVRM6UUDYqtwlDvwRJvo0LzvgyxGj9TmjqM5OJANBw5eIaRhUw629AAaD2EM4thoK1twEWldcqi0kT/tJadgon3CLp0kwMvrcmwa2GG7q8pyCecFKdRhvI2zmJbN2sFeMXHg8VzI4l5oKCoVLkAxyp+VQLwlVExX3sPasnCas0EwksPEHg24bymwfy4iiHFIydfNz2iJ7K27LgYwOv8gqqNLQm3LNUtT4lHDVSdJzEEQaBo2LYhBcp7579wi1i8Q5Jt/YyCsCuGj/cEPrUZ+CuNnySJfsnn5yb7g82k/Q1H3vxXkA== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000001, 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 Thu, 3 Apr 2025 at 15:47, Zhongkun He wro= te: > > On Wed, Apr 2, 2025 at 9:42=E2=80=AFPM Michal Koutn=C3=BD wrote: > > > > On Thu, Mar 20, 2025 at 08:33:09AM -0700, Shakeel Butt wrote: > > > However I want us to discuss and decide the semantics of > > > memsw from scratch rather than adopting v1 semantics. > > > > +1 > > > > > Also we should discuss how memsw and swap limits would interact and > > > what would be the appropriate default. > > > > Besides more complicated implementation, merged memsw won't represent a= n > > actual resource. > > > > So I'd be interested in use cases (other than "used to it from v1") tha= t > > cannot be controlled with separate memory. and swap. limits. > > > > Hi Michal > > We encountered an issue, which is also a real use case. With memory offlo= ading, > we can move some cold pages to swap. Suppose an application=E2=80=99s pea= k memory > usage at certain times is 10GB, while at other times, it exists in a > combination of > memory and swap. If we set limits on memory or swap separately, it would = lack > flexibility=E2=80=94sometimes it needs 1GB memory + 9GB swap, sometimes 5= GB > memory + 5GB swap, or even 10GB memory + 0GB swap. Therefore, we strongly > hope to use the mem+swap charging method in cgroupv2 > > > > > 0.02=E2=82=AC, > > Michal Yes, in the container scenario, if swap is enabled on the server and the customer's container requires 10GB of memory, we only need to set memory.memsw.limit_in_bytes=3D10GB, and the kernel can automatically swap o= ut part of the business container's memory to swap according to the server's m= emory pressure, and it can be fully guaranteed that the customer's container will not use more memory because swap is enabled on the server. >