[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160831211618.GA12660@htj.duckdns.org>
Date: Wed, 31 Aug 2016 17:16:18 -0400
From: Tejun Heo <tj@...nel.org>
To: Matan Barak <matanb@...lanox.com>
Cc: Parav Pandit <pandit.parav@...il.com>, 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, hch@....de, liranl@...lanox.com,
sean.hefty@...el.com, jgunthorpe@...idianresearch.com,
haggaie@...lanox.com, corbet@....net, james.l.morris@...cle.com,
serge@...lyn.com, ogerlitz@...lanox.com, akpm@...ux-foundation.org,
linux-security-module@...r.kernel.org
Subject: Re: [PATCHv12 1/3] rdmacg: Added rdma cgroup controller
Hello,
On Wed, Aug 31, 2016 at 06:07:30PM +0300, Matan Barak wrote:
> Currently, there are some discussions regarding the RDMA ABI. The current
> proposed approach (after a lot of discussions in the OFVWG) is to have
> driver dependent object types rather than the fixed set of IB object types
> we have today.
> AFAIK, some vendors might want to use the RDMA subsystem for a different
> fabrics which has a different set of objects.
> You could see RFCs for such concepts both from Mellanox and Intel on the
> linux-rdma mailing list.
>
> Saying that, maybe we need to make the resource types a bit more flexible
> and dynamic.
That'd be back to square one and Christoph was dead against it too,
so...
Thanks.
--
tejun
Powered by blists - more mailing lists