From: Tejun Heo <tj@kernel.org>
To: Parav Pandit <pandit.parav@gmail.com>
Cc: cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
lizefan@huawei.com, hannes@cmpxchg.org, dledford@redhat.com,
liranl@mellanox.com, sean.hefty@intel.com,
jgunthorpe@obsidianresearch.com, haggaie@mellanox.com,
corbet@lwn.net, james.l.morris@oracle.com, serge@hallyn.com,
ogerlitz@mellanox.com, matanb@mellanox.com,
akpm@linux-foundation.org, linux-security-module@vger.kernel.org,
hch@lst.de
Subject: Re: [PATCHv11 0/3] rdmacg: IB/core: rdma controller support
Date: Wed, 24 Aug 2016 17:17:47 -0400 [thread overview]
Message-ID: <20160824211747.GV8185@htj.duckdns.org> (raw)
In-Reply-To: <1471869231-15576-1-git-send-email-pandit.parav@gmail.com>
(cc'ing Christoph)
On Mon, Aug 22, 2016 at 06:03:48PM +0530, Parav Pandit wrote:
> rdmacg: IB/core: rdma controller support
>
> Patch is generated and tested against below Doug's linux-rdma
> git tree.
>
> URL: git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git
> Branch: master
>
> Patchset is also compiled and tested against below Tejun's cgroup tree
> using cgroup v2 mode.
> URL: git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
> Branch: master
>
> 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 kernel space ULPs may not even get chance
> to allocate any rdma resources. This results into service unavailibility.
>
> RDMA cgroup addresses this issue by allowing resource accounting,
> limit enforcement on per cgroup, per rdma device basis.
>
> RDMA uverbs layer will enforce limits on well defined RDMA verb
> resources without any HCA vendor device driver involvement.
>
> RDMA uverbs layer will not do limit enforcement of HCA hw vendor
> specific resources. Instead rdma cgroup provides set of APIs
> through which vendor specific drivers can do resource accounting
> by making use of rdma cgroup.
>
> Resource limit enforcement is hierarchical.
>
> When process is migrated with active RDMA resources, rdma cgroup
> continues to uncharge original cgroup for allocated resource. New resource
> is charged to current process's cgroup, which means if the process is
> migrated with active resources, for new resources it will be charged to
> new cgroup and old resources will be correctly uncharged from old cgroup.
>
> Changes from v10:
> * (To address comments from Tejun, Christoph)
> 1. Removed unused rpool_list_lock from rdma_cgroup structure.
> 2. Moved rdma resource definition to rdma cgroup instead of IB stack
> 3. Added prefix rdmacg to static instances
> 4. Simplified locking with single mutex for all operations
> 5. Following approach of atomically allocating object and
> charging resource in hirerchy
> 6. Code simplification due to single lock
> 7. Using for_each_set_bit API for bit operation
> 8. Renamed list heads as Objects instead of _head
> 9. Renamed list entries as _node instead of _list.
> 10. Made usage_num to 64 bit to avoid overflow and to avoid
> additional code to track non zero number of usage counts.
> * (To address comments from Doug)
> 1. Added copyright and GPLv2 license
Looks good to me. I just have a nit in the documentation. Christoph,
what do you think?
Thanks.
--
tejun
next prev parent reply other threads:[~2016-08-24 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:33 [PATCHv11 0/3] rdmacg: IB/core: rdma controller support Parav Pandit
2016-08-22 12:33 ` [PATCHv11 1/3] rdmacg: Added rdma cgroup controller Parav Pandit
2016-08-22 12:33 ` [PATCHv11 2/3] IB/core: added support to use " Parav Pandit
2016-08-22 12:33 ` [PATCHv11 3/3] rdmacg: Added documentation for rdmacg Parav Pandit
2016-08-24 21:18 ` Tejun Heo
2016-08-24 22:55 ` Rami Rosen
2016-08-25 7:58 ` Parav Pandit
2016-08-24 21:17 ` Tejun Heo [this message]
2016-08-25 7:32 ` [PATCHv11 0/3] rdmacg: IB/core: rdma controller support Christoph Hellwig
2016-08-25 8:00 ` Parav Pandit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160824211747.GV8185@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=haggaie@mellanox.com \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=james.l.morris@oracle.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=liranl@mellanox.com \
--cc=lizefan@huawei.com \
--cc=matanb@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=pandit.parav@gmail.com \
--cc=sean.hefty@intel.com \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).