From: Tejun Heo <tj@kernel.org>
To: Hongfu Li <lihongfu@kylinos.cn>
Cc: hannes@cmpxchg.org, mkoutny@suse.com, corbet@lwn.net,
skhan@linuxfoundation.org, dev@lankhorst.se, mripard@kernel.org,
natalie.vock@gmx.de, cgroups@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] cgroup/dmem: add per-region event counters
Date: Wed, 24 Jun 2026 08:52:47 -1000 [thread overview]
Message-ID: <ajwnf0uzT4PMHYZx@slm.duckdns.org> (raw)
In-Reply-To: <20260624031107.667253-2-lihongfu@kylinos.cn>
On Wed, Jun 24, 2026 at 11:11:06AM +0800, Hongfu Li wrote:
> Add dmem.events to report hierarchical low/max event counts per DMEM
> region. Increment counters on dmem.max allocation failures and
> dmem.low protection events. The file is available for non-root cgroups
> only.
Please don't double space in descs or comments. Also, maybe it's obvious but
it'd help if you list why and how this is useful. Why do we want to add
this?
> + dmem.events
> + A read-only file that reports the number of times each cgroup
> + has hit its configured memory limits. The format lists each
> + region on a single line, followed by the event counters::
> +
> + drm/0000:03:00.0/vram0 low 0 max 3
> + drm/0000:03:00.0/stolen low 0 max 0
This isn't a supported file format. Please read the documentation on allowed
formats.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-06-24 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 3:11 [PATCH 0/2] cgroup/dmem: add per-region event counters Hongfu Li
2026-06-24 3:11 ` [PATCH 1/2] " Hongfu Li
2026-06-24 18:52 ` Tejun Heo [this message]
2026-06-25 2:10 ` Hongfu Li
2026-06-25 8:57 ` Natalie Vock
2026-06-25 10:21 ` Hongfu Li
2026-06-24 3:11 ` [PATCH 2/2] cgroup/dmem: introduce dmem.events.local for local counts Hongfu Li
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=ajwnf0uzT4PMHYZx@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=hannes@cmpxchg.org \
--cc=lihongfu@kylinos.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=mripard@kernel.org \
--cc=natalie.vock@gmx.de \
--cc=skhan@linuxfoundation.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