[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150908152340.GA13749@mtj.duckdns.org>
Date: Tue, 8 Sep 2015 11:23:40 -0400
From: Tejun Heo <tj@...nel.org>
To: Parav Pandit <pandit.parav@...il.com>
Cc: cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
lizefan@...wei.com, hannes@...xchg.org, dledford@...hat.com,
corbet@....net, james.l.morris@...cle.com, serge@...lyn.com,
haggaie@...lanox.com, ogerlitz@...lanox.com, matanb@...lanox.com,
raindel@...lanox.com, akpm@...ux-foundation.org,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH 0/7] devcg: device cgroup extension for rdma resource
Hello, Parav.
On Tue, Sep 08, 2015 at 02:08:16AM +0530, Parav Pandit wrote:
> 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 kernel space ULPs may not even get chance
> to allocate any rdma resources.
Is there something simple I can read up on what each resource is?
What's the usual access control mechanism?
> This patch-set allows limiting rdma resources to set of processes.
> It extend device cgroup controller for limiting rdma device limits.
I don't think this belongs to devcg. If these make sense as a set of
resources to be controlled via cgroup, the right way prolly would be a
separate controller.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists