From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Usama Arif <usamaarif642@gmail.com>,
hannes@cmpxchg.org, tj@kernel.org, lizefan.x@bytedance.com,
nphamcs@gmail.com, corbet@lwn.net
Cc: 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: Fri, 3 May 2024 15:20:17 +0700 [thread overview]
Message-ID: <ZjSeQaPR90gV61xp@archie.me> (raw)
In-Reply-To: <20240502185307.3942173-2-usamaarif642@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Thu, May 02, 2024 at 07:50:24PM +0100, Usama Arif wrote:
> 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.
> +
> + 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
LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-05-03 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 18:50 [PATCH v2 0/1] cgroup: Add documentation for missing zswap memory.stat Usama Arif
2024-05-02 18:50 ` [PATCH v2 1/1] " Usama Arif
2024-05-02 23:28 ` Nhat Pham
2024-05-03 8:20 ` Bagas Sanjaya [this message]
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=ZjSeQaPR90gV61xp@archie.me \
--to=bagasdotme@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=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 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.