From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [Workman-devel] cgroup: status-quo and userland efforts Date: Mon, 8 Apr 2013 11:49:51 -0700 Message-ID: <20130408184951.GK3021@htj.dyndns.org> References: <20130406012159.GA17159@mtj.dyndns.org> <20130408175925.GE28292@redhat.com> <20130408181607.GI3021@htj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20130408181607.GI3021-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Vivek Goyal Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Kay Sievers , lpoetter-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, dhaval.giani-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, workman-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org List-Id: containers.vger.kernel.org On Mon, Apr 08, 2013 at 11:16:07AM -0700, Tejun Heo wrote: > > Given the fact that library has view of full system resoruces (both > > persistent view and active view), shouldn't we just be able to extend > > the API to meet additional configuration or resource needs. > > Maybe, I don't know. It just looks like a weird approach to me. > Wouldn't it make more sense to implement it as a dbus service that > everyone talks to? That's how our base system is structured these > days. Why should this be any different? To expand a bit, the base system being composed that way makes a lot of sense. It becomes clear who's responsible for what and there's a reliable way to recover when things go awry on the clients' sides. Also, it pretty much *forces* you to design an interface which fits the problem domain properly rather than exposing all the control knobs there are without thinking how they'd be actually useful. The language binding issue is much easier too - it's already solved. It seems like the only logical thing to do, well, at least to me. Am I missing something? Thanks. -- tejun From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935680Ab3DHSt7 (ORCPT ); Mon, 8 Apr 2013 14:49:59 -0400 Received: from mail-pa0-f44.google.com ([209.85.220.44]:48282 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935303Ab3DHSt4 (ORCPT ); Mon, 8 Apr 2013 14:49:56 -0400 Date: Mon, 8 Apr 2013 11:49:51 -0700 From: Tejun Heo To: Vivek Goyal Cc: Li Zefan , containers@lists.linux-foundation.org, cgroups@vger.kernel.org, bsingharora@gmail.com, Kay Sievers , lpoetter@redhat.com, linux-kernel@vger.kernel.org, dhaval.giani@gmail.com, workman-devel@redhat.com Subject: Re: [Workman-devel] cgroup: status-quo and userland efforts Message-ID: <20130408184951.GK3021@htj.dyndns.org> References: <20130406012159.GA17159@mtj.dyndns.org> <20130408175925.GE28292@redhat.com> <20130408181607.GI3021@htj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130408181607.GI3021@htj.dyndns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 08, 2013 at 11:16:07AM -0700, Tejun Heo wrote: > > Given the fact that library has view of full system resoruces (both > > persistent view and active view), shouldn't we just be able to extend > > the API to meet additional configuration or resource needs. > > Maybe, I don't know. It just looks like a weird approach to me. > Wouldn't it make more sense to implement it as a dbus service that > everyone talks to? That's how our base system is structured these > days. Why should this be any different? To expand a bit, the base system being composed that way makes a lot of sense. It becomes clear who's responsible for what and there's a reliable way to recover when things go awry on the clients' sides. Also, it pretty much *forces* you to design an interface which fits the problem domain properly rather than exposing all the control knobs there are without thinking how they'd be actually useful. The language binding issue is much easier too - it's already solved. It seems like the only logical thing to do, well, at least to me. Am I missing something? Thanks. -- tejun