From: Johannes Weiner <hannes@cmpxchg.org>
To: Usama Arif <usamaarif642@gmail.com>
Cc: tj@kernel.org, lizefan.x@bytedance.com, nphamcs@gmail.com,
corbet@lwn.net, linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH] cgroup: Add documentation for missing zswap memory.stat
Date: Wed, 1 May 2024 08:02:05 -0400 [thread overview]
Message-ID: <20240501120205.GB2538005@cmpxchg.org> (raw)
In-Reply-To: <20240501095349.1407643-1-usamaarif642@gmail.com>
On Wed, May 01, 2024 at 10:53:49AM +0100, Usama Arif wrote:
> This includes zswpin, zswpout and zswpwb.
Good idea adding these!
> Signed-off-by: Usama Arif <usamaarif642@gmail.com>
> ---
> Documentation/admin-guide/cgroup-v2.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> index 17e6e9565156..48ec54627814 100644
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -1454,6 +1454,15 @@ PAGE_SIZE multiple when read back.
> zswapped
> Amount of application memory swapped out to zswap.
>
> + zswpin
> + Number of pages moved in to memory from zswap.
> +
> + zswpout
> + Number of pages moved out of memory to zswap.
> +
> + zswpwb
> + Number of pages written from zswap to swap.
> +
They should go between pglazyfreed and thp_fault_alloc to match the
output ordering (they're event counters, not memory counters).
> file_mapped
> Amount of cached filesystem data mapped with mmap()
>
prev parent reply other threads:[~2024-05-01 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 9:53 [PATCH] cgroup: Add documentation for missing zswap memory.stat Usama Arif
2024-05-01 12:02 ` Johannes Weiner [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=20240501120205.GB2538005@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=kernel-team@meta.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=nphamcs@gmail.com \
--cc=tj@kernel.org \
--cc=usamaarif642@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).