From: Andrew Morton <akpm@linux-foundation.org>
To: Huan Yang <link@vivo.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeelb@google.com>,
Muchun Song <muchun.song@linux.dev>,
Suleiman Souhlal <suleiman@google.com>,
Mike Rapoport <rppt@kernel.org>,
"Jan Alexander Steffens (heftig)" <heftig@archlinux.org>,
Yu Zhao <yuzhao@google.com>, Brian Geffon <bgeffon@google.com>,
Gaosheng Cui <cuigaosheng1@huawei.com>,
Peter Xu <peterx@redhat.com>,
Axel Rasmussen <axelrasmussen@google.com>,
"T.J. Alumbaugh" <talumbau@google.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, cgroups@vger.kernel.org, kernel@vivo.com
Subject: Re: [PATCH 0/3] Per memcg lru_gen node stat
Date: Wed, 27 Sep 2023 10:38:52 -0700 [thread overview]
Message-ID: <20230927103852.971afee31402fceb5f0fa529@linux-foundation.org> (raw)
In-Reply-To: <20230914104754.55-1-link@vivo.com>
On Thu, 14 Sep 2023 18:47:42 +0800 Huan Yang <link@vivo.com> wrote:
> On original global lru_gen node in debugfs, it can all show each memcg's
> lru gen info in "lru_gen" or "lru_gen_full", and can type cmd into lru_gen.
> But which show info contains all memcg's info, and cmd need to
> know memcg's id.
>
> This patchset add lru_gen node in per memcg, with this node, we can
> get lru_gen info in each memcg.
> Also, we can type cmd to control each memcg's lru_gen seq, but, this node
> don't support multi cmd, single memcg just process one cmd once time.
Strangely, I cannot find this series in my linux-mm archive. They came
through in linux-kernel however.
Perhaps a resend will help move things along, thanks.
parent reply other threads:[~2023-09-27 17:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230914104754.55-1-link@vivo.com>]
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=20230927103852.971afee31402fceb5f0fa529@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=bgeffon@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=cuigaosheng1@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=heftig@archlinux.org \
--cc=kernel@vivo.com \
--cc=link@vivo.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=peterx@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=suleiman@google.com \
--cc=talumbau@google.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yuzhao@google.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