From mboxrd@z Thu Jan 1 00:00:00 1970 From: Balbir Singh Subject: Re: [Devel] OLS paper topics Date: Wed, 30 Jan 2008 22:24:59 +0530 Message-ID: <47A0ABE3.6020803@linux.vnet.ibm.com> References: <20080123195736.GA7823@sergelap.austin.ibm.com> <47990BAB.4050106@openvz.org> <20080124225002.GC13819@sergelap.austin.ibm.com> <47A03A73.6070408@openvz.org> <47A03C25.8030205@linux.vnet.ibm.com> <47A04916.50904@fr.ibm.com> <47A04A7A.9030701@linux.vnet.ibm.com> <20080130155220.GD1206@sergelap.austin.ibm.com> Reply-To: balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080130155220.GD1206-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@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: "Serge E. Hallyn" Cc: Kir Kolyshkin , Linux Containers , Cedric Le Goater List-Id: containers.vger.kernel.org Serge E. Hallyn wrote: > Quoting Balbir Singh (balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org): >> Cedric Le Goater wrote: >>>>> == Topic == >>>>> >>>>> Namespaces, containers, cgroups, and container checkpoint/restart. >>>>> >>>>> == Description == >>>>> >>>>> Development for namespaces and cgroups is well underway in the >>>>> mainline kernel. To keep momentum going and keep the loosely >>>>> knit teams of developers well-coordinated, a physical meeting in >>>>> which to discuss future development plans is needed. >>>>> Additionally, we are at a point where crucial decisions about >>>>> the nature of a "container object" and about the checkpoint/restart >>>>> design need to be made. >>>>> >>>>> A final set of topics will be decided upon through mailing lists >>>>> ahead of time, but potential topics include: >>>>> * Handling filesystem/namespace synchronization >>>>> * Handling of /proc and /sysfs within containers >>>>> * Additional needed namespaces (i.e. device namespace) >>>>> * Nature of a 'container' ??? kernel object or userspace fiction >>>>> * Additional cgroups and their design >>>>> * How to initiate and synchronize checkpoint/restart >>>>> * How to enter a 'container' ? >>>>> >>>> Resource Management for containers? >>> Yes we need that. There are a few possible conflicts in requirements >>> that need to be discussed. For example, a resource management req >>> would be to be able to move a process from one group to another and C/R >>> wouldn't. >> Cedric, >> >> Why is that a conflict w.r.t resource management, isn't that more of a cgroup >> feature - task migration. > > Oh, no - I think Cedric was saying that tasks need to be moved from > container2 to container3 on the system for resourcemgmt - that is, > reclassified, not migrated. > OK, so the concern is with automatic reclassification > But for task migration we have resources tied to containers and > processes are using those resources, so we can't migrate those tasks to > another container in that case. > > That's probably solved at the cgroup->container bindings, no? i.e. > ns_cgroup 2854 is my container and it's in a cpuset_cgroup tied to cpus > 2 and 3, now i want to open it up to cpus 1-4, so i leave the tasks in > ns_cgroup 2854 but move it to another cpuset... > Yes, I agree -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL