On 01/02/2016 20:59, Parav Pandit wrote: > On Tue, Feb 2, 2016 at 12:10 AM, Tejun Heo <tj@xxxxxxxxxx> wrote: >> So, I'm really not gonna go for individual drivers defining resources >> on their own. That's a trainwreck waiting to happen. There needs to >> be a lot more scrutiny than that. >> > Not every low level driver. I started with that infrastructure in > v2,v3 but I got your inputs and > I align with that. It could be just single IB stack in one header file > in one enum list would be sufficient. > You have already given that example. > With that mostly two resource type that I have can also shrink to just > single type. > Will wait to hear from them, in case if they have any different thought. Hi, Sorry for the late reply. I think that starting with the standard set of resources that uverbs provide is good, and if we need in the future new types of resources we can add them later. On 31/01/2016 19:50, Parav Pandit wrote: > How would you like to see RDMA verb resources being defined - in RDMA > cgroup or in IB stack? > In current patch v5, its defined by the IB stack which is often > shipped as different package due to high amount of changes, bug fixes, > features. > In v0 patch it was defined by the RDMA cgroup, which means any new > resource addition/definition requires kernel upgrade. Which is hard to > change often. There is indeed an effort to backport the latest RDMA subsystem modules to older kernels, and it would be preferable to be able to introduce new resources through these modules. However, I understand that there are no other cgroups that are modules or depend on modules this way, so I would understand if you decide against it. > If resources are defined by RDMA cgroup kernel than adding/removing > resource means, someone have to do lot of engineering with different > versions of kernel support and loadable module support using compat.h > etc at driver level, which in my mind is some amount of engineering > compare to what v5 has to offer and its already available. With one > round of cleanup in resource definition, it should be usable. If I understand correctly, if the resources are defined in the cgroup, you simply won't be able to add new resources with a module update, no matter how hard you work. I agree that if the cgroup code is changed for cleanup or whatever reason, the backporting may become difficult, but that's just life. > Its important to provide this feedback to Tejun and me, so that we > take informed design decision. Sure. I hope this patchset gets accepted eventually, as I believe it solves a real problem. Today RDMA application can easily hog these resources and the rdma cgroup allows users to prevent that. Regards, Haggai -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
