Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Tejun Heo <tj@kernel.org>
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: Tue, 18 Aug 2026 11:51:48 +0200	[thread overview]
Message-ID: <66ff58b7b0396106898cfc54c73240a0dcaaf049.camel@linux.intel.com> (raw)
In-Reply-To: <aoILQuck_EuxQgVh@slm.duckdns.org>

On Sun, 2026-08-16 at 09:10 -1000, Tejun Heo wrote:
> 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?

Certainly. I think a main concern though would be testing of the
existing use-cases. But anyway I'll take a look in that direction.

Thanks,
Thomas

> 
> Thanks.

      reply	other threads:[~2026-08-18  9:52 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
2026-08-18  9:51   ` Thomas Hellström [this message]

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=66ff58b7b0396106898cfc54c73240a0dcaaf049.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