Re: [Workman-devel] cgroup: status-quo and userland efforts

2015-03-03 Thread Luke Leighton
Serge Hallyn writes: > > Quoting Daniel P. Berrange (berrange@...): > > Are you also planning to actually write a new cgroup parent manager > > daemon too ? Currently my plan for libvirt is to just talk directly > > I'm toying with the idea, yes. (Right now my toy runs in either native > mode

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-07-23 Thread Michal Hocko
On Mon 15-07-13 14:49:40, Vivek Goyal wrote: > On Sun, Jun 30, 2013 at 08:38:38PM +0200, Michal Hocko wrote: > > On Fri 28-06-13 14:01:55, Vivek Goyal wrote: > > > On Fri, Jun 28, 2013 at 05:05:13PM +0200, Michal Hocko wrote: > > [...] > > > > OK, so libcgroup's rules daemon will still work and pla

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-07-15 Thread Vivek Goyal
On Sun, Jun 30, 2013 at 08:38:38PM +0200, Michal Hocko wrote: > On Fri 28-06-13 14:01:55, Vivek Goyal wrote: > > On Fri, Jun 28, 2013 at 05:05:13PM +0200, Michal Hocko wrote: > [...] > > > OK, so libcgroup's rules daemon will still work and place my tasks in > > > appropriate cgroups? > > > > Do y

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-30 Thread Michal Hocko
On Fri 28-06-13 14:01:55, Vivek Goyal wrote: > On Fri, Jun 28, 2013 at 05:05:13PM +0200, Michal Hocko wrote: [...] > > OK, so libcgroup's rules daemon will still work and place my tasks in > > appropriate cgroups? > > Do you use that daemon in practice? I am not but my users do. And that is why I

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-28 Thread Tejun Heo
On Fri, Jun 28, 2013 at 05:40:53PM -0500, Serge Hallyn wrote: > > The kernel can exposed a knob that would allow systemd to lock that > > down > > Gah - why would you give him that idea? :) That's one of the ideas I had from the beginning. > But yes, I'd sort of assume that was coming, eventual

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-28 Thread Serge Hallyn
Quoting Daniel P. Berrange (berra...@redhat.com): > On Fri, Jun 28, 2013 at 02:01:55PM -0400, Vivek Goyal wrote: > > On Fri, Jun 28, 2013 at 05:05:13PM +0200, Michal Hocko wrote: > > > On Thu 27-06-13 22:01:38, Tejun Heo wrote: > > > > Hello, Mike. > > > > > > > > On Fri, Jun 28, 2013 at 06:49:10A

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-28 Thread Daniel P. Berrange
On Fri, Jun 28, 2013 at 02:01:55PM -0400, Vivek Goyal wrote: > On Fri, Jun 28, 2013 at 05:05:13PM +0200, Michal Hocko wrote: > > On Thu 27-06-13 22:01:38, Tejun Heo wrote: > > > Hello, Mike. > > > > > > On Fri, Jun 28, 2013 at 06:49:10AM +0200, Mike Galbraith wrote: > > > > I always thought that w

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-28 Thread Tim Hockin
On Fri, Jun 28, 2013 at 8:53 AM, Serge Hallyn wrote: > Quoting Daniel P. Berrange (berra...@redhat.com): >> Are you also planning to actually write a new cgroup parent manager >> daemon too ? Currently my plan for libvirt is to just talk directly > > I'm toying with the idea, yes. (Right now my

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-28 Thread Vivek Goyal
On Fri, Jun 28, 2013 at 05:05:13PM +0200, Michal Hocko wrote: > On Thu 27-06-13 22:01:38, Tejun Heo wrote: > > Hello, Mike. > > > > On Fri, Jun 28, 2013 at 06:49:10AM +0200, Mike Galbraith wrote: > > > I always thought that was a very cool feature, mkdir+echo, poof done. > > > Now maybe that inter

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-28 Thread Serge Hallyn
Quoting Daniel P. Berrange (berra...@redhat.com): > On Thu, Jun 27, 2013 at 08:22:06AM -0500, Serge Hallyn wrote: > > FWIW, the code is too embarassing yet to see daylight, but I'm playing > > with a very lowlevel cgroup manager which supports nesting itself. > > Access in this POC is low-level ("s

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-06-28 Thread Daniel P. Berrange
On Thu, Jun 27, 2013 at 08:22:06AM -0500, Serge Hallyn wrote: > FWIW, the code is too embarassing yet to see daylight, but I'm playing > with a very lowlevel cgroup manager which supports nesting itself. > Access in this POC is low-level ("set freezer.state to THAWED for cgroup > /c1/c2", "Create /

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Tejun Heo
On Mon, Apr 08, 2013 at 03:46:31PM -0400, Vivek Goyal wrote: > It would be good to think more about it. How a user can ensure minimum > resources to a partition/service. Because in that case at every level > somebody needs to keep track how much of resources have been committed > as minimum require

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Vivek Goyal
On Mon, Apr 08, 2013 at 12:20:24PM -0700, Tejun Heo wrote: [..] > > For example, one might want to say that maximum IO bandwidth for > > virtual machine virt1 on disk sda should be 10MB/s. Now libvirt > > should be able to save it in virtual machine specific configuration > > easily and whenever

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Tejun Heo
Hey, On Mon, Apr 08, 2013 at 03:11:05PM -0400, Vivek Goyal wrote: > > What if the program crashes? > > I am not sure about this. I guess when applications comes back after crash, > it can go through all the children cgroups and reclaim empty cgroups. Fragile, right? What are you arguing here?

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Vivek Goyal
On Mon, Apr 08, 2013 at 11:16:07AM -0700, Tejun Heo wrote: > Hey, Vivek. > > On Mon, Apr 08, 2013 at 01:59:26PM -0400, Vivek Goyal wrote: > > But using the library admin application should be able to query the > > full "paritition" hierarchy and their weigths and calculate % system > > resources.

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Tejun Heo
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

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Tejun Heo
Hey, Vivek. On Mon, Apr 08, 2013 at 01:59:26PM -0400, Vivek Goyal wrote: > But using the library admin application should be able to query the > full "paritition" hierarchy and their weigths and calculate % system > resources. I think one problem there is cpu controller where % resoruce > of a cgr

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Vivek Goyal
On Mon, Apr 08, 2013 at 05:46:09PM +0400, Glauber Costa wrote: [..] > The cpu cgroup needs a real-time timeslice to accept real time tasks. It > defaults to 0, meaning that a newly created cpu cgroup cannot accept > tasks (rt tasks) without the user having to manually configure it. > As far as I k

Re: [Workman-devel] cgroup: status-quo and userland efforts

2013-04-08 Thread Vivek Goyal
On Fri, Apr 05, 2013 at 06:21:59PM -0700, Tejun Heo wrote: [..] > Userland efforts > > > There are currently a few userland efforts trying to make interfacing > with cgroup less painful. > > * libcg: Make cgroup interface accessible from programming languages > with support