Hi Leon, Christoph, Matan, Tejun, Thanks for the update. I need some more information in order to roll out new patch. Inline clarification below. On Thu, Nov 3, 2016 at 11:30 PM, Leon Romanovsky <leon@xxxxxxxxxx> wrote: > On Tue, Nov 01, 2016 at 04:33:23PM +0530, Parav Pandit wrote: >> So my opinion is: >> (a) Let cgroup define the current standard objects and new reasonable >> set of vendor specific objects in future. >> (b) Add new rdma.percentage parameter so that any new standard object >> or vendor specific object can be abstracted from average end user and >> applications which are yet to catch up. >> I believe this takes care of your point (1), (3), (4)? > > We (Tejun, Christoph, Matan and me) had a face-to-face talk during > KS/LPC and decided that the best way to move forward is to export to > user one object (global HCA like) only and don't export anything else. > Can you please confirm the below points to make sure design fits-in. 1. so rdma.current and rdma.max, will show one overall current percentage used and configured? (Instead of per object absolute value) 2. As a starting point minimum percentage will be 1%. Default will be 100%. 3. So for example if user has configured 2% of resource, this 2% will be applicable as 2% of MR, 2% of QP and so on. 4. rdma cgroup continues to do accounting, resource definition as done in patch_v12. Though there is provision for defining handful of vendor specific objects in rdma cgroup, we don't define is currently and therefore they won't be accounted. 5. In future when such need arise to account vendor specific objects, they will be added to rdma cgroup. > All internal calculations will be based on this percentage. > > Once the cgroups users will come with reasonable justification why they > need to configure different unexposed objects, we will expose them. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
