From: Nhat Pham <nphamcs@gmail.com>
To: Usama Arif <usamaarif642@gmail.com>
Cc: hannes@cmpxchg.org, tj@kernel.org, lizefan.x@bytedance.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 v2 1/1] cgroup: Add documentation for missing zswap memory.stat
Date: Thu, 2 May 2024 16:28:46 -0700 [thread overview]
Message-ID: <CAKEwX=OUf6Rd2aEwcEYdO_D3ALrSMCTdO4fdpiqhO-F-ygyLfw@mail.gmail.com> (raw)
In-Reply-To: <20240502185307.3942173-2-usamaarif642@gmail.com>
On Thu, May 2, 2024 at 11:53 AM Usama Arif <usamaarif642@gmail.com> wrote:
>
> This includes zswpin, zswpout and zswpwb.
>
> 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..eaf9e66e472a 100644
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -1572,6 +1572,15 @@ PAGE_SIZE multiple when read back.
> pglazyfreed (npn)
> Amount of reclaimed lazyfree pages
>
> + zswpin
> + Number of pages moved in to memory from zswap.
nit: into?
> +
> + zswpout
> + Number of pages moved out of memory to zswap.
> +
> + zswpwb
> + Number of pages written from zswap to swap.
> +
> thp_fault_alloc (npn)
> Number of transparent hugepages which were allocated to satisfy
> a page fault. This counter is not present when CONFIG_TRANSPARENT_HUGEPAGE
> --
> 2.43.0
>
That very small nit aside, LGTM. Thanks for completing the documentation.
Acked-by: Nhat Pham <nphamcs@gmail.com>
next prev parent reply other threads:[~2024-05-02 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 18:50 [PATCH v2 0/1] " Usama Arif
2024-05-02 18:50 ` [PATCH v2 1/1] " Usama Arif
2024-05-02 23:28 ` Nhat Pham [this message]
2024-05-03 8:20 ` Bagas Sanjaya
2024-05-03 14:54 ` Johannes Weiner
2024-05-09 16:53 ` Jonathan Corbet
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='CAKEwX=OUf6Rd2aEwcEYdO_D3ALrSMCTdO4fdpiqhO-F-ygyLfw@mail.gmail.com' \
--to=nphamcs@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--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=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