Hi Tejun, On Wed, Jan 6, 2016 at 3:26 AM, Tejun Heo <t...@kernel.org> wrote: > Hello, > > On Wed, Jan 06, 2016 at 12:28:00AM +0530, Parav Pandit wrote: >> Resources are not defined by the RDMA cgroup. Resources are defined >> by RDMA/IB stack & optionally by HCA vendor device drivers. > > As I wrote before, I don't think this is a good idea. Drivers will > inevitably add non-sensical "resources" which don't make any sense > without much scrutiny.
In our last discussion on v0 patch, http://lkml.iu.edu/hypermail/linux/kernel/1509.1/04331.html The direction was, that vendor should be able to define their own resources. > If different controllers can't agree upon the > same set of resources, which probably is a pretty good sign that this > isn't too well thought out to begin with, When you said "different controller" you meant "different hw vendors", right? Or you meant, rdma, mem, cpu as controller here? > at least make all resource > types defined by the controller itself and let the controllers enable > them selectively. > In this V1 patch, resource is defined by the IB stack and rdma cgroup is facilitator for same. By doing so, IB stack modules can define new resource without really making changes to cgroup. This design also allows hw vendors to define their own resources which will be reviewed in rdma mailing list anway. The idea is different hw versions can have different resource support, so the whole intention is not about defining different resource but rather enabling it. But yes, I equally agree that by doing so, different hw controller vendors can define different hw resources. > Thanks. > > -- > tejun -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html