All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Yu Miao <yumiao@kylinos.cn>
Cc: cgroups@vger.kernel.org, hannes@cmpxchg.org, mkoutny@suse.com,
	corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	jiayuan.chen@shopee.com, nphamcs@gmail.com
Subject: Re: [PATCH v2] Docs/admin-guide/cgroup-v2: fix npn tags in memory.stat
Date: Wed, 18 Nov 2026 22:53:55 -1000	[thread overview]
Message-ID: <74ad05b502dc12632e7a831be7641388@kernel.org> (raw)
In-Reply-To: <20261118130537.750211-1-yumiao@kylinos.cn>

On Wed, Nov 18, 2026 at 09:05:37PM +0800, Yu Miao wrote:
> The zswap, zswapped, zswap_incomp, swpin_zero, swpout_zero, zswpin,
> zswpout and zswpwb entries never show up in memory.numa_stat, so add
> the 'npn' tag to them.  The pgscan_kswapd, pgscan_direct,
> pgscan_khugepaged, pgscan_proactive, pgsteal_kswapd, pgsteal_direct,
> pgsteal_khugepaged, pgsteal_proactive and pgrefill entries do show up
> in memory.numa_stat since commit e4f4fc7aa8b7 ("mm: move pgscan,
> pgsteal, pgrefill to node stats"), so remove their 'npn' tag.
> Also move zswap_incomp, currently listed between the zswpwb and
> thp_fault_alloc counters, next to the zswap and zswapped entries
> it belongs with.
>
> Signed-off-by: Yu Miao <yumiao@kylinos.cn>

Acked-by: Tejun Heo <tj@kernel.org>

Thanks.

--
tejun

      parent reply	other threads:[~2026-11-19  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  6:26 [PATCH] Docs/admin-guide/cgroup-v2: add missing npn tags to zswap stats Yu Miao
2026-11-17 21:20 ` Tejun Heo
2026-11-18 13:05 ` [PATCH v2] Docs/admin-guide/cgroup-v2: fix npn tags in memory.stat Yu Miao
2026-11-18 16:09   ` Nhat Pham
2026-11-19  8:53   ` Tejun Heo [this message]

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=74ad05b502dc12632e7a831be7641388@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=jiayuan.chen@shopee.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mkoutny@suse.com \
    --cc=nphamcs@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=yumiao@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.