From: Matan Barak <matanb@mellanox.com>
To: Tejun Heo <tj@kernel.org>
Cc: Parav Pandit <pandit.parav@gmail.com>, <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>, <hch@lst.de>,
<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>, <akpm@linux-foundation.org>,
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCHv12 1/3] rdmacg: Added rdma cgroup controller
Date: Thu, 1 Sep 2016 10:25:40 +0300 [thread overview]
Message-ID: <9b6a346d-af4c-1e5f-0144-f68fb8e46c27@mellanox.com> (raw)
In-Reply-To: <20160831211618.GA12660@htj.duckdns.org>
On 01/09/2016 00:16, Tejun Heo wrote:
> 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...
>
Well, if I recall, the reason doing so last time was in order to allow
flexible updating of ib_core independently, which is obviously not a
good reason (to say the least).
Since the new ABI will probably define new object types (all recent
proposals go this way), the current approach could lead to either trying
to map new objects to existing cgroup resource types, which could lead
to some weird non 1:1 mapping, or having a split definitions - such that
each driver will declare its objects both in the cgroups mechanism and
in its driver dispatch table.
Even worse than that, drivers could simply ignore the cgroups support
while implementing their own resource types and get a very broken
containers support.
> Thanks.
>
Matan
next prev parent reply other threads:[~2016-09-01 12:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:37 [PATCHv12 0/3] rdmacg: IB/core: rdma controller support Parav Pandit
2016-08-31 8:37 ` [PATCHv12 1/3] rdmacg: Added rdma cgroup controller Parav Pandit
2016-08-31 9:38 ` Leon Romanovsky
2016-09-07 15:07 ` Parav Pandit
2016-09-08 6:12 ` Leon Romanovsky
2016-09-08 10:20 ` Parav Pandit
2016-08-31 15:07 ` Matan Barak
2016-08-31 21:16 ` Tejun Heo
2016-09-01 7:25 ` Matan Barak [this message]
2016-09-01 8:44 ` Christoph Hellwig
2016-09-07 7:55 ` Parav Pandit
2016-09-07 8:51 ` Matan Barak
2016-09-07 14:54 ` Parav Pandit
2016-09-10 16:14 ` Christoph Hellwig
2016-09-10 17:01 ` Jason Gunthorpe
2016-09-11 8:07 ` Matan Barak
2016-09-11 13:34 ` Christoph Hellwig
2016-09-11 14:35 ` Leon Romanovsky
2016-09-11 17:14 ` Jason Gunthorpe
2016-09-11 17:24 ` Christoph Hellwig
2016-09-11 17:52 ` Jason Gunthorpe
2016-09-12 5:07 ` Leon Romanovsky
2016-09-14 7:06 ` Parav Pandit
2016-09-14 8:14 ` Matan Barak
2016-09-14 9:19 ` Parav Pandit
2016-09-15 18:56 ` Leon Romanovsky
2016-09-21 4:43 ` Parav Pandit
2016-09-21 14:26 ` Tejun Heo
2016-09-21 16:02 ` Parav Pandit
2016-10-04 18:19 ` Parav Pandit
2016-10-05 6:37 ` Christoph Hellwig
2016-10-05 11:22 ` Leon Romanovsky
2016-10-05 15:36 ` Tejun Heo
2016-10-06 12:55 ` Parav Pandit
2016-10-18 20:15 ` Parav Pandit
2016-09-19 13:10 ` Dalessandro, Dennis
2016-09-19 17:00 ` Parav Pandit
2016-09-10 16:12 ` Christoph Hellwig
2016-09-11 7:40 ` Matan Barak
2016-08-31 8:37 ` [PATCHv12 2/3] IB/core: added support to use " Parav Pandit
2016-08-31 8:37 ` [PATCHv12 3/3] rdmacg: Added documentation for rdmacg Parav Pandit
2016-08-31 13:56 ` [PATCHv12 0/3] rdmacg: IB/core: rdma controller support Tejun Heo
2016-10-05 11:22 ` Leon Romanovsky
2016-10-06 12:59 ` 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=9b6a346d-af4c-1e5f-0144-f68fb8e46c27@mellanox.com \
--to=matanb@mellanox.com \
--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=ogerlitz@mellanox.com \
--cc=pandit.parav@gmail.com \
--cc=sean.hefty@intel.com \
--cc=serge@hallyn.com \
--cc=tj@kernel.org \
/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).