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 9CE7BC433F5 for ; Sat, 21 May 2022 16:37:34 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 36F826B0072; Sat, 21 May 2022 12:37:34 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 31DDE6B0073; Sat, 21 May 2022 12:37:34 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2350B6B0078; Sat, 21 May 2022 12:37:34 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 169946B0072 for ; Sat, 21 May 2022 12:37:34 -0400 (EDT) Received: from smtpin03.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id E5A09609B9 for ; Sat, 21 May 2022 16:37:33 +0000 (UTC) X-FDA: 79490305986.03.1ACBFF3 Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) by imf22.hostedemail.com (Postfix) with ESMTP id 8832CC0013 for ; Sat, 21 May 2022 16:37:30 +0000 (UTC) Received: by mail-lj1-f174.google.com with SMTP id v9so3385971lja.12 for ; Sat, 21 May 2022 09:37:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openvz-org.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:from:subject:to:cc :references:content-language:in-reply-to:content-transfer-encoding; bh=sDPyJk/btvhatfZsy9I1gg0gfPUmSvuPo0Lq5BQOpLA=; b=w0eAuvC1VimJE+5Y6Ul7B8d99Tt3m0U7Mq5SCjFVRP+LIrx1VAIl5jhjm9Y6ws+Nq/ sa4C6fBJJuf1YCUpoXziOi9FVrgS20OWgmQGZGfuw/AxCksANsD4+FKblvWnSUxHi1Tm 7YOwJ/JaXsvQt/oPBbQyRlYmMP3MapyUzce8ZV/cUMRkXPGu8IbuLLE4pbV+9jPHbT2C VWA+4Ws9XIxlBbstWFv+zSYUwvyPyG1miULKWiWegTq+2bjydr4NlmlTHQml0D4kD04H 5h9akhPprZnHU2KwQ7iJq7nAqNREMH2dxVsBynUvSg+OPR/jHPuAunz9y5BrtePg2w+c Mvvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:from :subject:to:cc:references:content-language:in-reply-to :content-transfer-encoding; bh=sDPyJk/btvhatfZsy9I1gg0gfPUmSvuPo0Lq5BQOpLA=; b=UjdIMpHaPBDgs4s5bKdimhYhoh1s8QHLqQlLgTTc7DLC6NTh3uRH2ue+hk0fp/cpKL preEsfXObegzUq3Cel5tbeSF69AcDC4A82f/nqviPeM9OykYQ6TlizVRqLAphLDqKmgw HCNUgv4uy1db2HUrBlWgooyzHqoiIG6gbOkeowxS0PpoXaE3PPhOT9oCCw58UVAZf4JB RcMQH+nbOt7EiJ5aLe+TwaIzGy/bHU2+u31GurCLhA3mRtWuCNdlKfavu4b5NDFNL7BX 4np28SG9fhPvRrJZGC9n0qWeb8dJOFGm8ZURJFctpGLfc/nKL8XxkLm2o2glp+LgD39m vneA== X-Gm-Message-State: AOAM532WQlL2iMZ5NuUgMhhyeS2ylPlUQd/91eQz2RLE9OaTUoP3mRoq BMtrmgG2zzvM77ud9gEVC04chg== X-Google-Smtp-Source: ABdhPJx9bRomX57NPPN44lZtBUkGEl22UMv4x/n8IeaiMawe0gF84i1pF4KIgrhIyv32BDLaRcXD1g== X-Received: by 2002:a2e:a585:0:b0:24f:528f:3621 with SMTP id m5-20020a2ea585000000b0024f528f3621mr8568109ljp.416.1653151051132; Sat, 21 May 2022 09:37:31 -0700 (PDT) Received: from [192.168.1.65] ([46.188.121.185]) by smtp.gmail.com with ESMTPSA id v5-20020a056512348500b004744d5f8f26sm1117380lfr.52.2022.05.21.09.37.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 21 May 2022 09:37:30 -0700 (PDT) Message-ID: <06505918-3b8a-0ad5-5951-89ecb510138e@openvz.org> Date: Sat, 21 May 2022 19:37:29 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 From: Vasily Averin Subject: [PATCH mm v2 0/9] memcg: accounting for objects allocated by mkdir cgroup To: Andrew Morton Cc: kernel@openvz.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Shakeel Butt , Roman Gushchin , =?UTF-8?Q?Michal_Koutn=c3=bd?= , Vlastimil Babka , Michal Hocko , cgroups@vger.kernel.org References: Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 8832CC0013 X-Stat-Signature: soqhyyc31gc3mt3ai6wewuzzm7bpsa6d X-Rspam-User: Authentication-Results: imf22.hostedemail.com; dkim=pass header.d=openvz-org.20210112.gappssmtp.com header.s=20210112 header.b=w0eAuvC1; spf=pass (imf22.hostedemail.com: domain of vvs@openvz.org designates 209.85.208.174 as permitted sender) smtp.mailfrom=vvs@openvz.org; dmarc=pass (policy=none) header.from=openvz.org X-HE-Tag: 1653151050-569649 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: Below is tracing results of mkdir /sys/fs/cgroup/vvs.test on 4cpu VM with Fedora and self-complied upstream kernel. The calculations are not precise, it depends on kernel config options, number of cpus, enabled controllers, ignores possible page allocations etc. However this is enough to clarify the general situation. All allocations are splited into: - common part, always called for each cgroup type - per-cgroup allocations In each group we consider 2 corner cases: - usual allocations, important for 1-2 CPU nodes/Vms - percpu allocations, important for 'big irons' common part: ~11Kb + 318 bytes percpu memcg: ~17Kb + 4692 bytes percpu cpu: ~2.5Kb + 1036 bytes percpu cpuset: ~3Kb + 12 bytes percpu blkcg: ~3Kb + 12 bytes percpu pid: ~1.5Kb + 12 bytes percpu perf: ~320b + 60 bytes percpu ------------------------------------------- total: ~38Kb + 6142 bytes percpu currently accounted: 4668 bytes percpu - it's important to account usual allocations called in common part, because almost all of cgroup-specific allocations are small. One exception here is memory cgroup, it allocates a few huge objects that should be accounted. - Percpu allocation called in common part, in memcg and cpu cgroups should be accounted, rest ones are small an can be ignored. - KERNFS objects are allocated both in common part and in most of cgroups Details can be found here: https://lore.kernel.org/all/d28233ee-bccb-7bc3-c2ec-461fd7f95e6a@openvz.org/ I checked other cgroups types was found that they all can be ignored. Additionally I found allocation of struct rt_rq called in cpu cgroup if CONFIG_RT_GROUP_SCHED was enabled, it allocates huge (~1700 bytes) percpu structure and should be accounted too. v2: 1) re-split to simplify possible bisect, re-ordered 2) added accounting for percpu psi_group_cpu and cgroup_rstat_cpu, allocated in common part 3) added accounting for percpu allocation of struct rt_rq (actual if CONFIG_RT_GROUP_SCHED is enabled) 4) improved patches descriptions Vasily Averin (9): memcg: enable accounting for struct cgroup memcg: enable accounting for kernfs nodes memcg: enable accounting for kernfs iattrs memcg: enable accounting for struct simple_xattr memcg: enable accounting for percpu allocation of struct psi_group_cpu memcg: enable accounting for percpu allocation of struct cgroup_rstat_cpu memcg: enable accounting for large allocations in mem_cgroup_css_alloc memcg: enable accounting for allocations in alloc_fair_sched_group memcg: enable accounting for percpu allocation of struct rt_rq fs/kernfs/mount.c | 6 ++++-- fs/xattr.c | 2 +- kernel/cgroup/cgroup.c | 2 +- kernel/cgroup/rstat.c | 3 ++- kernel/sched/fair.c | 4 ++-- kernel/sched/psi.c | 3 ++- kernel/sched/rt.c | 2 +- mm/memcontrol.c | 4 ++-- 8 files changed, 15 insertions(+), 11 deletions(-) -- 2.36.1