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
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
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
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
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
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
6 matches
Mail list logo