From: Domenico Cerasuolo <cerasuolodomenico@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, surenb@google.com, brauner@kernel.org,
chris@chrisdown.name, hannes@cmpxchg.org,
Domenico Cerasuolo <cerasuolodomenico@gmail.com>
Subject: [PATCH v2 0/3] sched/psi: Allow unprivileged PSI polling
Date: Thu, 23 Mar 2023 11:33:47 +0100 [thread overview]
Message-ID: <20230323103350.40569-1-cerasuolodomenico@gmail.com> (raw)
PSI offers 2 mechanisms to get information about a specific resource
pressure. One is reading from /proc/pressure/<resource>, which gives
average pressures aggregated every 2s. The other is creating a pollable
fd for a specific resource and cgroup.
The trigger creation requires CAP_SYS_RESOURCE, and gives the
possibility to pick specific time window and threshold, spawing an RT
thread to aggregate the data.
Systemd would like to provide containers the option to monitor pressure
on their own cgroup and sub-cgroups. For example, if systemd launches a
container that itself then launches services, the container should have
the ability to poll() for pressure in individual services. But neither
the container nor the services are privileged.
The series is implemented in 3 steps in order to reduce the noise of
the change.
V2:
- removed renaming patch (previous 2/4) and applied suggested solution
- changed update_triggers side effect removal as suggested in review
- rebased core patch on other V2 changes
Domenico Cerasuolo (3):
sched/psi: rearrange polling code in preparation
sched/psi: extract update_triggers side effect
sched/psi: allow unprivileged polling of N*2s period
Documentation/accounting/psi.rst | 4 +
include/linux/psi.h | 2 +-
include/linux/psi_types.h | 11 +-
kernel/cgroup/cgroup.c | 2 +-
kernel/sched/psi.c | 315 ++++++++++++++++---------------
5 files changed, 181 insertions(+), 153 deletions(-)
--
2.34.1
next reply other threads:[~2023-03-23 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 10:33 Domenico Cerasuolo [this message]
2023-03-23 10:33 ` [PATCH v2 1/3] sched/psi: rearrange polling code in preparation Domenico Cerasuolo
2023-03-23 10:33 ` [PATCH v2 2/3] sched/psi: extract update_triggers side effect Domenico Cerasuolo
2023-03-23 10:33 ` [PATCH v2 3/3] sched/psi: allow unprivileged polling of N*2s period Domenico Cerasuolo
2023-03-23 15:09 ` Johannes Weiner
2023-03-23 16:43 ` Suren Baghdasaryan
2023-03-23 17:40 ` Johannes Weiner
2023-03-23 16:55 ` Suren Baghdasaryan
2023-03-23 17:44 ` Johannes Weiner
2023-03-23 18:07 ` Suren Baghdasaryan
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=20230323103350.40569-1-cerasuolodomenico@gmail.com \
--to=cerasuolodomenico@gmail.com \
--cc=brauner@kernel.org \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=surenb@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