From: Tejun Heo <tj@kernel.org>
To: Xingyou Chen <rockrush@rockwork.org>
Cc: Vipin Sharma <vipinsh@google.com>,
mkoutny@suse.com, jacob.jun.pan@intel.com, rdunlap@infradead.org,
thomas.lendacky@amd.com, brijesh.singh@amd.com,
jon.grimm@amd.com, eric.vantassell@amd.com, pbonzini@redhat.com,
hannes@cmpxchg.org, frankja@linux.ibm.com,
borntraeger@de.ibm.com, brian.welty@intel.com, corbet@lwn.net,
seanjc@google.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
gingell@google.com, rientjes@google.com, kvm@vger.kernel.org,
x86@kernel.org, cgroups@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] cgroup: New misc cgroup controller
Date: Thu, 23 Sep 2021 06:01:09 -1000 [thread overview]
Message-ID: <YUykxX/oWh2kvOvQ@slm.duckdns.org> (raw)
In-Reply-To: <f1955267-c009-4dea-970e-9145c7cd6dbc@rockwork.org>
On Thu, Sep 23, 2021 at 11:38:49PM +0800, Xingyou Chen wrote:
> > Misc controller is a generic controller which can be used by these
> > kinds of resources.
>
> Will we make this dynamic? Let resources be registered via something
> like misc_cg_res_{register,unregister}, at compile time or runtime,
> instead of hard coded into misc_res_name/misc_res_capacity etc.
>
> There are needs as noted in drmcg session earlier this year. We may
> make misc cgroup stable, and let device drivers to register their
> own resources.
Not too likely given that the need for one-off resources for a specific
driver seems to indicate lack of proper abstraction and control mechanism
more than anything else. Even for cases where there are genuine needs for
per-hardware knobs, I think it's prudent to enforce a review cycle which
involves people who aren't directly working on the specific driver.
Thanks.
--
tejun
prev parent reply other threads:[~2021-09-23 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 4:42 [PATCH v4 0/3] cgroup: New misc cgroup controller Vipin Sharma
2021-03-30 4:42 ` [PATCH v4 1/3] cgroup: Add " Vipin Sharma
2021-03-30 4:42 ` [PATCH v4 2/3] cgroup: Miscellaneous cgroup documentation Vipin Sharma
2021-03-30 4:42 ` [PATCH v4 3/3] svm/sev: Register SEV and SEV-ES ASIDs to the misc controller Vipin Sharma
2021-04-04 17:35 ` [PATCH v4 0/3] cgroup: New misc cgroup controller Tejun Heo
2021-04-05 0:29 ` Vipin Sharma
2021-09-23 15:35 ` Xingyou Chen
2021-09-23 15:38 ` Xingyou Chen
2021-09-23 16:01 ` Tejun Heo [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=YUykxX/oWh2kvOvQ@slm.duckdns.org \
--to=tj@kernel.org \
--cc=borntraeger@de.ibm.com \
--cc=bp@alien8.de \
--cc=brian.welty@intel.com \
--cc=brijesh.singh@amd.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=eric.vantassell@amd.com \
--cc=frankja@linux.ibm.com \
--cc=gingell@google.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--cc=jmattson@google.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=rockrush@rockwork.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vipinsh@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).