From: "Michal Koutný" <mkoutny@suse.com>
To: Daniel Sedlak <daniel.sedlak@cdn77.com>,
Shakeel Butt <shakeel.butt@linux.dev>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
David Ahern <dsahern@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
linux-mm@kvack.org, netdev@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
cgroups@vger.kernel.org, Matyas Hurtik <matyas.hurtik@cdn77.com>
Subject: Re: [PATCH v3] memcg: expose socket memory pressure in a cgroup
Date: Tue, 22 Jul 2025 10:57:31 +0200 [thread overview]
Message-ID: <ni4axiks6hvap3ixl6i23q7grjbki3akeea2xxzhdlkmrj5hpb@qt3vtmiayvpz> (raw)
In-Reply-To: <20250722071146.48616-1-daniel.sedlak@cdn77.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Hello Daniel.
On Tue, Jul 22, 2025 at 09:11:46AM +0200, Daniel Sedlak <daniel.sedlak@cdn77.com> wrote:
> /sys/fs/cgroup/**/<cgroup name>/memory.net.socket_pressure
>
> The output value is an integer matching the internal semantics of the
> struct mem_cgroup for socket_pressure. It is a periodic re-arm clock,
> representing the end of the said socket memory pressure, and once the
> clock is re-armed it is set to jiffies + HZ.
I don't find it ideal to expose this value in its raw form that is
rather an implementation detail.
IIUC, the information is possibly valid only during one jiffy interval.
How would be the userspace consuming this?
I'd consider exposing this as a cummulative counter in memory.stat for
simplicity (or possibly cummulative time spent in the pressure
condition).
Shakeel, how useful is this vmpressure per-cgroup tracking nowadays? I
thought it's kind of legacy.
Thanks,
Michal
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-07-22 8:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 7:11 Daniel Sedlak
2025-07-22 7:17 ` Eric Dumazet
2025-07-22 7:27 ` Daniel Sedlak
2025-07-22 8:57 ` Michal Koutný [this message]
2025-07-22 17:50 ` Shakeel Butt
2025-07-22 18:27 ` Kuniyuki Iwashima
2025-07-22 18:41 ` Waiman Long
2025-07-22 18:49 ` Kuniyuki Iwashima
2025-07-22 19:05 ` Shakeel Butt
2025-07-22 19:58 ` Kuniyuki Iwashima
2025-07-22 20:11 ` Shakeel Butt
2025-07-22 22:10 ` Kuniyuki Iwashima
2025-07-23 8:38 ` Michal Koutný
2025-07-23 8:58 ` Daniel Sedlak
2025-07-23 17:54 ` Shakeel Butt
2025-07-24 8:43 ` Daniel Sedlak
2025-07-25 0:44 ` Tejun Heo
2025-07-28 11:29 ` Daniel Sedlak
2025-07-30 0:15 ` Tejun Heo
2025-07-23 8:41 ` Daniel Sedlak
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=ni4axiks6hvap3ixl6i23q7grjbki3akeea2xxzhdlkmrj5hpb@qt3vtmiayvpz \
--to=mkoutny@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.sedlak@cdn77.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=hannes@cmpxchg.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-mm@kvack.org \
--cc=matyas.hurtik@cdn77.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=yosry.ahmed@linux.dev \
/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