From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Tejun Heo <tj@kernel.org>, maarten.lankhorst@linux.intel.com
Cc: intel-xe@lists.freedesktop.org, cgroups@vger.kernel.org,
dri-devel@lists.freedesktop.org, pallavi.mishra@intel.com
Subject: [RFC] dmisc cgroups controller
Date: Fri, 14 Aug 2026 11:32:54 +0200 [thread overview]
Message-ID: <894f9d44eae62aee5762495b4f90f9bdd2b5585d.camel@linux.intel.com> (raw)
Hi!
We (drm/xe GPU driver) have a use-case where we have a very limited
number of a particular device resource (CLOS slots) that we potentially
want to expose to unprivlieged processes for reservation / allocation.
We want to be able to restrict per cgroups the number of CLOS slots
that are available for reservation / allocation.
This is not a good fit for the misc controller since these resource
types may be added and removed similar to dmem regions. Neither is it a
good fit for the dmem controller.
Would a dmisc controller be suitable here? It would be similar to the
misc countroller but with dynamic addition and removal of resource
types similar to the dmem controller.
Any input greatly appreciated.
Thanks,
Thomas
reply other threads:[~2026-08-14 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=894f9d44eae62aee5762495b4f90f9bdd2b5585d.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=cgroups@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=pallavi.mishra@intel.com \
--cc=tj@kernel.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