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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 183CBC433E4 for ; Tue, 30 Mar 2021 21:11:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CA18A619C2 for ; Tue, 30 Mar 2021 21:10:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232717AbhC3VKa (ORCPT ); Tue, 30 Mar 2021 17:10:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47818 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232585AbhC3VKI (ORCPT ); Tue, 30 Mar 2021 17:10:08 -0400 Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D6E22C061762 for ; Tue, 30 Mar 2021 14:10:06 -0700 (PDT) Received: by mail-qk1-x730.google.com with SMTP id c4so17342311qkg.3 for ; Tue, 30 Mar 2021 14:10:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpxchg-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=rpUNagm8tKUALZ2s8mUVHZFt+lniACSUPOUh0BnW38A=; b=0Y97W8BZj0o5jjujWGFPPRAY2G8hnfCb3yd+FbzrNcXfO70LDuA1Ke+UfSwNyPf5EP 0ZcNOaR9XlZ1GucL/K/5QnXXuXa+pqwfptcOdpscNtlUfN9EZoxHwZQAG3bd+x+rX7lJ 6uQe4j2boTuN2YVpbRg8xNET3kQRsc3iEUzKebIeQKqz2FEenRr0uErHGa8k2hjMZyqR DS1Xbkt+zQCo7Rw7UhUscBI77QTYJy7gcxlgzDolOKtO8L56Hc/t6bqFYEyWwkHrw1E8 zWU+kmTcTO6nIt4jmc40Ni5q14DruJpajIdt0omXteARz1hCch4Wo+MG6QD537UORQW8 i3ig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=rpUNagm8tKUALZ2s8mUVHZFt+lniACSUPOUh0BnW38A=; b=qX0mzOVU2v/kVqa0RRCzOQleopajSWaDSUd8D8yd6BzMFtUBfovDQkILeszydjoVKv Dko3kfoRd+7Z3x44oExGf1qbqzoyKF7qKHei2vKMWyhZyhlYHI1Q6KQjPgM+Tl76KRDY zlWsgkdpD+T6/ymEP6y0CM7OkAYKvkaJFFu5AcqgMOWwqkZ4NrZrJ+NcDbZUxnEaMzb/ r33EC8rOt3kIkWeYwlyftsrbVe5xIoYeanTx6pKmKqzRklCF8iDXGNvOZyxm/sBoWqY0 C5SOUh3bGtk+oMNLNFZT14FPEyDxjd3flDwgiENQifsQyC9jA1GVjTCELJBiooBdtSYz KUXg== X-Gm-Message-State: AOAM533782m3jSSx3aRNAICl/kww16+J1TWoumViYOZo5xhchc03rUZ7 wlUkNUSUOsH9gJl+7WK9gunZrw== X-Google-Smtp-Source: ABdhPJymG8dspAGp3Odl1swBNMXvZejWrldV3MZ3LYFMvCx9qpMwC6nApTcIp1kTdQnMUAqA8dUIdA== X-Received: by 2002:a05:620a:819:: with SMTP id s25mr162734qks.485.1617138606035; Tue, 30 Mar 2021 14:10:06 -0700 (PDT) Received: from localhost (70.44.39.90.res-cmts.bus.ptd.net. [70.44.39.90]) by smtp.gmail.com with ESMTPSA id c7sm127482qtv.48.2021.03.30.14.10.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 Mar 2021 14:10:05 -0700 (PDT) Date: Tue, 30 Mar 2021 17:10:04 -0400 From: Johannes Weiner To: Shakeel Butt Cc: Muchun Song , Greg Thelen , Roman Gushchin , Michal Hocko , Andrew Morton , Vladimir Davydov , LKML , Linux MM , Xiongchun duan Subject: Re: [RFC PATCH 00/15] Use obj_cgroup APIs to charge the LRU pages Message-ID: References: <20210330101531.82752-1-songmuchun@bytedance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 30, 2021 at 11:34:11AM -0700, Shakeel Butt wrote: > On Tue, Mar 30, 2021 at 3:20 AM Muchun Song wrote: > > > > Since the following patchsets applied. All the kernel memory are charged > > with the new APIs of obj_cgroup. > > > > [v17,00/19] The new cgroup slab memory controller > > [v5,0/7] Use obj_cgroup APIs to charge kmem pages > > > > But user memory allocations (LRU pages) pinning memcgs for a long time - > > it exists at a larger scale and is causing recurring problems in the real > > world: page cache doesn't get reclaimed for a long time, or is used by the > > second, third, fourth, ... instance of the same job that was restarted into > > a new cgroup every time. Unreclaimable dying cgroups pile up, waste memory, > > and make page reclaim very inefficient. > > > > We can convert LRU pages and most other raw memcg pins to the objcg direction > > to fix this problem, and then the LRU pages will not pin the memcgs. > > > > This patchset aims to make the LRU pages to drop the reference to memory > > cgroup by using the APIs of obj_cgroup. Finally, we can see that the number > > of the dying cgroups will not increase if we run the following test script. > > > > ```bash > > #!/bin/bash > > > > cat /proc/cgroups | grep memory > > > > cd /sys/fs/cgroup/memory > > > > for i in range{1..500} > > do > > mkdir test > > echo $$ > test/cgroup.procs > > sleep 60 & > > echo $$ > cgroup.procs > > echo `cat test/cgroup.procs` > cgroup.procs > > rmdir test > > done > > > > cat /proc/cgroups | grep memory > > ``` > > > > Patch 1 aims to fix page charging in page replacement. > > Patch 2-5 are code cleanup and simplification. > > Patch 6-15 convert LRU pages pin to the objcg direction. > > The main concern I have with *just* reparenting LRU pages is that for > the long running systems, the root memcg will become a dumping ground. > In addition a job running multiple times on a machine will see > inconsistent memory usage if it re-accesses the file pages which were > reparented to the root memcg. I don't understand how Muchun's patches are supposed to *change* the behavior the way you are describing it. This IS today's behavior. We have hierarchical accounting, and a page that belongs to a leaf cgroup will automatically belong to all its parents. Further, if you delete a cgroup today, the abandoned cache will stay physically linked to that cgroup, but that zombie group no longer acts as a control structure: it imposes no limit and no protection; the pages will be reclaimed as if it WERE linked to the parent. For all intents and purposes, when you delete a cgroup today, its remaining pages ARE dumped onto the parent. The only difference is that today they pointlessly pin the leaf cgroup as a holding vessel - which is then round-robin'd from the parent during reclaim in order to pretend that all these child pages actually ARE linked to the parent's LRU list. Remember how we used to have every page physically linked to multiple lrus? The leaf cgroup and the root? All pages always belong to the (virtual) LRU list of all ancestor cgroups. The only thing Muchun changes is that they no longer pin a cgroup that has no semantical meaning anymore (because it's neither visible to the user nor exerts any contol over the pages anymore). Maybe I'm missing something that either you or Roman can explain to me. But this series looks like a (rare) pure win. Whether you like the current semantics is a separate discussion IMO. > Please note that I do agree with the mentioned problem and we do see > this issue in our fleet. Internally we have a "memcg mount option" > feature which couples a file system with a memcg and all file pages > allocated on that file system will be charged to that memcg. Multiple > instances (concurrent or subsequent) of the job will use that file > system (with a dedicated memcg) without leaving the zombies behind. I > am not pushing for this solution as it comes with its own intricacies > (e.g. if memcg coupled with a file system has a limit, the oom > behavior would be awkward and therefore internally we don't put a > limit on such memcgs). Though I want this to be part of discussion. Right, you disconnect memory from the tasks that are allocating it, and so you can't assign culpability when you need to. OOM is one thing, but there are also CPU cycles and IO bandwidth consumed during reclaim. > I think the underlying reasons behind this issue are: > > 1) Filesystem shared by disjoint jobs. > 2) For job dedicated filesystems, the lifetime of the filesystem is > different from the lifetime of the job. There is also the case of deleting a cgroup just to recreate it right after for the same job. Many job managers do this on restart right now - like systemd, and what we're using in our fleet. This seems avoidable by recycling a group for another instance of the same job. Sharing is a more difficult discussion. If you access a page that you share with another cgroup, it may or may not be subject to your own or your buddy's memory limits. The only limit it is guaranteed to be subjected to is that of your parent. So One thing I could imagine is, instead of having a separate cgroup outside the hierarchy, we would reparent live pages the second they are accessed from a foreign cgroup. And reparent them until you reach the first common ancestor. This way, when you mount a filesystem shared by two jobs, you can put them into a joint subtree, and the root level of this subtree captures all the memory (as well as the reclaim CPU and IO) used by the two jobs - the private portions and the shared portions - and doesn't make them the liability of jobs in the system that DON'T share the same fs. But again, this is a useful discussion to have, but I don't quite see why it's relevant to Muchun's patches. They're purely an optimization. So I'd like to clear that up first before going further.