From: Georgi Djakov <djakov@kernel.org>
To: Michal Hocko <mhocko@suse.com>,
Georgi Djakov <quic_c_gdjako@quicinc.com>
Cc: hannes@cmpxchg.org, vincent.guittot@linaro.org,
juri.lelli@redhat.com, peterz@infradead.org, mingo@redhat.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vdavydov.dev@gmail.com, tj@kernel.org,
axboe@kernel.dk, cgroups@vger.kernel.org,
linux-block@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] psi: Add additional PSI counters for each type of memory pressure
Date: Wed, 10 Nov 2021 18:45:38 +0200 [thread overview]
Message-ID: <91db431e-d5db-be5c-b0d2-382e45786886@kernel.org> (raw)
In-Reply-To: <YYvuRUqcxW0Vu9vp@dhcp22.suse.cz>
On 10.11.21 18:07, Michal Hocko wrote:
> On Wed 10-11-21 07:36:37, Georgi Djakov wrote:
>> From: Carlos Ramirez <carlrami@codeaurora.org>
>>
>> Calculates psi totals for memory pressure subevents:
>> compaction, thrashing, direct compaction, direct reclaim, and kswapd0.
>> Uses upper 16 bits of psi_flags to track memory subevents.
>
> Could you elaborate on the definition of those events please? That
> should also go to Documentation (Documentation/accounting/psi.rst)
Sure, will add them to the Documentation! The idea is to add some
statistics for the memory pressure subevents that helps to figure
out the sources of the pressure. This is just an RFC to gather
initial feedback if such approach would be acceptable.
Thanks!
Georgi
next prev parent reply other threads:[~2021-11-10 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 15:36 Georgi Djakov
2021-11-10 16:07 ` Michal Hocko
2021-11-10 16:45 ` Georgi Djakov [this message]
2021-11-10 16:14 ` Peter Zijlstra
2021-11-10 16:45 ` Georgi Djakov
2021-11-10 17:48 ` Suren Baghdasaryan
2021-11-10 16:44 ` Johannes Weiner
2021-12-01 19:26 ` Georgi Djakov
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=91db431e-d5db-be5c-b0d2-382e45786886@kernel.org \
--to=djakov@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=vincent.guittot@linaro.org \
/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