public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Li Wang <liwang@redhat.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org
Cc: Christoph Lameter <cl@linux.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	Shakeel Butt <shakeelb@google.com>, Tejun Heo <tj@kernel.org>,
	Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH 2/2] selftests/cgroup: include slab in test_percpu_basic memory check
Date: Thu, 19 Mar 2026 15:38:19 -0400	[thread overview]
Message-ID: <5cf1d4fc-cab1-45f7-954f-ecebef2994bf@redhat.com> (raw)
In-Reply-To: <20260306071843.149147-2-liwang@redhat.com>

On 3/6/26 2:18 AM, Li Wang wrote:
> test_percpu_basic() currently compares memory.current against only
> memory.stat:percpu after creating 1000 child cgroups.
>
> Observed failure:
>    #./test_kmem
>    ok 1 test_kmem_basic
>    ok 2 test_kmem_memcg_deletion
>    ok 3 test_kmem_proc_kpagecgroup
>    ok 4 test_kmem_kernel_stacks
>    ok 5 test_kmem_dead_cgroups
>    memory.current 11530240
>    percpu 8440000
>    not ok 6 test_percpu_basic
>
> That assumption is too strict: child cgroup creation also allocates
> slab-backed metadata, so memory.current is expected to be larger than
> percpu alone. One visible path is:
>
>    cgroup_mkdir()
>      cgroup_create()
>        cgroup_addrm_file()
>          cgroup_add_file()
>            __kernfs_create_file()
>              __kernfs_new_node()
>                kmem_cache_zalloc()
>
> These kernfs allocations are charged as slab and show up in
> memory.stat:slab.
>
> Update the check to compare memory.current against (percpu + slab)
> within MAX_VMSTAT_ERROR, and print slab/delta in the failure message to
> improve diagnostics.
>
> Signed-off-by: Li Wang <liwang@redhat.com>
> Cc: Waiman Long <longman@redhat.com>
> Cc: Christoph Lameter <cl@linux.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Shakeel Butt <shakeelb@google.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Vlastimil Babka <vbabka@suse.cz>
> ---
>   tools/testing/selftests/cgroup/test_kmem.c | 11 ++++++-----
>   1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/selftests/cgroup/test_kmem.c b/tools/testing/selftests/cgroup/test_kmem.c
> index 249d79113067..4b5799698893 100644
> --- a/tools/testing/selftests/cgroup/test_kmem.c
> +++ b/tools/testing/selftests/cgroup/test_kmem.c
> @@ -353,7 +353,7 @@ static int test_percpu_basic(const char *root)
>   {
>   	int ret = KSFT_FAIL;
>   	char *parent, *child;
> -	long current, percpu;
> +	long current, percpu, slab;
>   	int i;
>   
>   	parent = cg_name(root, "percpu_basic_test");
> @@ -379,13 +379,14 @@ static int test_percpu_basic(const char *root)
>   
>   	current = cg_read_long(parent, "memory.current");
>   	percpu = cg_read_key_long(parent, "memory.stat", "percpu ");
> +	slab = cg_read_key_long(parent, "memory.stat", "slab ");
>   
> -	if (current > 0 && percpu > 0 && labs(current - percpu) <
> -	    MAX_VMSTAT_ERROR)
> +	if (current > 0 && percpu > 0 && slab >= 0 &&
> +			labs(current - (percpu + slab)) < MAX_VMSTAT_ERROR)
>   		ret = KSFT_PASS;
>   	else
> -		printf("memory.current %ld\npercpu %ld\n",
> -		       current, percpu);
> +		printf("memory.current %ld\npercpu %ld\nslab %ld\ndelta %ld\n",
> +			current, percpu, slab, current - (percpu + slab));
>   
>   cleanup_children:
>   	for (i = 0; i < 1000; i++) {
Reviewed-by: Waiman Long <longman@redhat.com>


  reply	other threads:[~2026-03-19 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  7:18 [PATCH 1/2] selftests/cgroup: Fix hardcoded page size in test_percpu_basic Li Wang
2026-03-06  7:18 ` [PATCH 2/2] selftests/cgroup: include slab in test_percpu_basic memory check Li Wang
2026-03-19 19:38   ` Waiman Long [this message]
2026-03-19 19:37 ` [PATCH 1/2] selftests/cgroup: Fix hardcoded page size in test_percpu_basic Waiman Long
2026-04-02  6:46 ` Li Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5cf1d4fc-cab1-45f7-954f-ecebef2994bf@redhat.com \
    --to=longman@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liwang@redhat.com \
    --cc=mhocko@kernel.org \
    --cc=shakeelb@google.com \
    --cc=tj@kernel.org \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox