Re: [PATCHv1 0/6] rdma controller support

2016-01-07 Thread Tejun Heo
Hello, Parav. On Thu, Jan 07, 2016 at 04:43:20AM +0530, Parav Pandit wrote: > > 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

Re: [PATCHv1 0/6] rdma controller support

2016-01-06 Thread Parav Pandit
Hi Tejun, On Wed, Jan 6, 2016 at 3:26 AM, Tejun Heo 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'

Re: [PATCHv1 0/6] rdma controller support

2016-01-05 Thread Tejun Heo
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

[PATCHv1 0/6] rdma controller support

2016-01-05 Thread Parav Pandit
This patchset adds support for RDMA cgroup by addressing review comments of [1] by implementing published RFC [2]. Overview: Currently user space applications can easily take away all the rdma device specific resources such as AH, CQ, QP, MR etc. Due to which other applications in other cgroup or