Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: maarten.lankhorst@linux.intel.com,
	intel-xe@lists.freedesktop.org, cgroups@vger.kernel.org,
	dri-devel@lists.freedesktop.org, pallavi.mishra@intel.com
Subject: Re: [RFC] dmisc cgroups controller
Date: Sun, 16 Aug 2026 09:10:58 -1000	[thread overview]
Message-ID: <aoILQuck_EuxQgVh@slm.duckdns.org> (raw)
In-Reply-To: <894f9d44eae62aee5762495b4f90f9bdd2b5585d.camel@linux.intel.com>

On Fri, Aug 14, 2026 at 11:32:54AM +0200, Thomas Hellström wrote:
> 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.

Would extending the existing misc controller be an option?

Thanks.

-- 
tejun

  reply	other threads:[~2026-08-16 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  9:32 [RFC] dmisc cgroups controller Thomas Hellström
2026-08-16 19:10 ` Tejun Heo [this message]
2026-08-18  9:51   ` Thomas Hellström

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=aoILQuck_EuxQgVh@slm.duckdns.org \
    --to=tj@kernel.org \
    --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=thomas.hellstrom@linux.intel.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