[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160910161228.GB29259@lst.de>
Date: Sat, 10 Sep 2016 18:12:28 +0200
From: Christoph Hellwig <hch@....de>
To: Parav Pandit <pandit.parav@...il.com>
Cc: Christoph Hellwig <hch@....de>, Matan Barak <matanb@...lanox.com>,
Tejun Heo <tj@...nel.org>, cgroups@...r.kernel.org,
linux-doc@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-rdma@...r.kernel.org, Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Doug Ledford <dledford@...hat.com>,
Liran Liss <liranl@...lanox.com>,
"Hefty, Sean" <sean.hefty@...el.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Haggai Eran <haggaie@...lanox.com>,
Jonathan Corbet <corbet@....net>, james.l.morris@...cle.com,
serge@...lyn.com, Or Gerlitz <ogerlitz@...lanox.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-security-module@...r.kernel.org
Subject: Re: [PATCHv12 1/3] rdmacg: Added rdma cgroup controller
On Wed, Sep 07, 2016 at 01:25:13PM +0530, Parav Pandit wrote:
> > a) delay cgroups support until the grand rewrite is done
> > b) add it now and deal with the consequences later
> >
> Can we do (b) now and differ adding any HW resources to cgroup until
> they are clearly called out.
> Architecture and APIs are already in place to support this.
Sounds fine to me. The only thing I want to avoid is pie in the
sky "future proofing" that leads to horrible architectures. And I assume
that's what Matan proposed.
Powered by blists - more mailing lists