From: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Timur Tabi <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Two newbie questions on containers
Date: Tue, 11 Jan 2011 18:02:26 -0600 [thread overview]
Message-ID: <1294790546.26638.36.camel@tp-t61> (raw)
In-Reply-To: <4D2CD4F7.9040006-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Hi Timur,
On Tue, 2011-01-11 at 16:08 -0600, Timur Tabi wrote:
> 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.
cgroups and the lxc utilities work just as well on powerpc as they do on
x86; there's nothing arch-specific about them.
> 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.
Not totally sure about this myself, but have you read
Documentation/cgroups/devices.txt in the kernel source yet?
next prev parent reply other threads:[~2011-01-12 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 22:08 Two newbie questions on containers Timur Tabi
[not found] ` <4D2CD4F7.9040006-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-01-12 0:02 ` Nathan Lynch [this message]
2011-01-12 14:17 ` Daniel Lezcano
2011-01-12 17:35 ` Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1294790546.26638.36.camel@tp-t61 \
--to=ntl-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox