From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Two newbie questions on containers Date: Tue, 11 Jan 2011 16:08:55 -0600 Message-ID: <4D2CD4F7.9040006@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: 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: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: containers.vger.kernel.org Hi, I'm in the process of learning about Linux containers, including cgroups, and the learning curve seems pretty steep to me. So I have a couple newbie questions for all of you. Any detailed answered are greatly appreciated. 1) For the PowerPC architecture, is there anything that is "missing"? I can't really tell how much of cgroups and lxc is architecture-specific, and there appears to be PowerPC support for both already. I'd like to know if this another one of those areas, like KVM, where x86 is fully implemented and PowerPC support is lagging. 2) Given a random device driver, like a driver for a serial port, is there an opportunity for the driver to be enhanced to support cgroups or lxc? Doing a simple search of the kernel source code, I don't really see any drivers making calls into any cgroup code, so I don't understand how to restrict device access to a specific container or cgroup. -- Timur Tabi Linux kernel developer at Freescale