On 10/09/2016 19:12, Christoph Hellwig wrote:
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.
NO, that not what I proposed. User-kernel API/ABI should be designed
with drivers differences in mind. The internal design or internals APIs
could ignore such things as they can be changed later.
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
