mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul Menage" <menage@google.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: "Linux Containers" <containers@lists.linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Control Groups Roadmap ideas
Date: Mon, 14 Apr 2008 08:03:57 -0700	[thread overview]
Message-ID: <6599ad830804140803p2a97c96mbc24f73e1a687aee@mail.gmail.com> (raw)
In-Reply-To: <20080414141119.GA11019@sergelap.austin.ibm.com>

On Mon, Apr 14, 2008 at 7:11 AM, Serge E. Hallyn <serue@us.ibm.com> wrote:
>
>  then all tasks are mapped under /containers.  If login does a
>  clone(CLONE_NEWNS) for hallyn's login to give him a private /tmp,
>  then hallyn ends up under /containers/node_xyz, but we don't want him
>  to be virtualized under there.  So I assume we'd want a virt.lock file
>  or something like that so, that when I create a container, my
>  start_container script can echo 1 > /containers/node_abc/virt.lock

Yes, something like that.

>
>  I assume the container will also have to remount a fresh copy of the
>  cgroup composition so it can have the dentry for /containers/node_abc
>  as the root dentry for /containers?

Yes.

Paul

      reply	other threads:[~2008-04-14 15:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 21:14 Paul Menage
2008-04-09  2:28 ` Li Zefan
2008-04-10 20:10   ` Paul Menage
2008-04-11 14:48 ` Serge E. Hallyn
2008-04-12  5:10   ` Balbir Singh
2008-04-13 16:11     ` Serge E. Hallyn
2008-04-14 14:31       ` Balbir Singh
2008-04-14  5:24   ` Paul Menage
2008-04-14 14:11     ` Serge E. Hallyn
2008-04-14 15:03       ` Paul Menage [this message]

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=6599ad830804140803p2a97c96mbc24f73e1a687aee@mail.gmail.com \
    --to=menage@google.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    /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

all inboxes | Powered by JetHome®