From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752652AbXCMXux (ORCPT ); Tue, 13 Mar 2007 19:50:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752647AbXCMXux (ORCPT ); Tue, 13 Mar 2007 19:50:53 -0400 Received: from MAIL.13thfloor.at ([213.145.232.33]:38128 "EHLO MAIL.13thfloor.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652AbXCMXuw (ORCPT ); Tue, 13 Mar 2007 19:50:52 -0400 Date: Wed, 14 Mar 2007 00:50:51 +0100 From: Herbert Poetzl To: Srivatsa Vaddagiri Cc: menage@google.com, xemul@sw.ru, dev@sw.ru, pj@sgi.com, sam@vilain.net, ebiederm@xmission.com, winget@google.com, serue@us.ibm.com, akpm@linux-foundation.org, containers@lists.osdl.org, linux-kernel@vger.kernel.org, ckrm-tech@lists.sourceforge.net Subject: Re: Summary of resource management discussion Message-ID: <20070313235051.GA5000@MAIL.13thfloor.at> Mail-Followup-To: Srivatsa Vaddagiri , menage@google.com, xemul@sw.ru, dev@sw.ru, pj@sgi.com, sam@vilain.net, ebiederm@xmission.com, winget@google.com, serue@us.ibm.com, akpm@linux-foundation.org, containers@lists.osdl.org, linux-kernel@vger.kernel.org, ckrm-tech@lists.sourceforge.net References: <20070312124226.GD17151@in.ibm.com> <20070313162459.GQ8755@MAIL.13thfloor.at> <20070313175820.GA21825@in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070313175820.GA21825@in.ibm.com> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 13, 2007 at 11:28:20PM +0530, Srivatsa Vaddagiri wrote: > On Tue, Mar 13, 2007 at 05:24:59PM +0100, Herbert Poetzl wrote: > > what about identifying different resource categories and > > handling them according to the typical usage pattern? > > > > like the following: > > > > - cpu and scheduler related accounting/limits > > - memory related accounting/limits > > - network related accounting/limits > > - generic/file system related accounting/limits > > > > I don't worry too much about having the generic/file stuff > > attached to the nsproxy, but the cpu/sched stuff might be > > better off being directly reachable from the task > > I think we should experiment with both combinations (a direct pointer > to cpu_limit structure from task_struct and an indirect pointer), get > some numbers and then decide. Or do you have results already with > respect to that? nope, no numbers for that, but I appreciate some testing and probably can do some testing in this regard too (although I want to get some testing done for the resource sharing between guests first) > > > 3. How are cpusets related to vserver/containers? > > > > > > Should it be possible to, lets say, create exclusive cpusets and > > > attach containers to different cpusets? > > > > that is what Linux-VServer does atm, i.e. you can put > > an entire guest into a specific cpu set > > Interesting. What abt /dev/cpuset view? host only for now best, Herbert > Is that same for all containers or do you restrict that view > to the containers cpuset only? > > -- > Regards, > vatsa > _______________________________________________ > Containers mailing list > Containers@lists.osdl.org > https://lists.osdl.org/mailman/listinfo/containers