LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
	Kirill Korotaev <dev@openvz.org>,
	Pavel Emelianov <xemul@openvz.org>,
	Cedric Le Goater <clg@fr.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-man@vger.kernel.org
Subject: Re: CLONE_NEWIPC documentation
Date: Sun, 23 Nov 2008 16:48:42 -0600	[thread overview]
Message-ID: <20081123224842.GD12687@hallyn.com> (raw)
In-Reply-To: <m163mji4cz.fsf@frodo.ebiederm.org>

Quoting Eric W. Biederman (ebiederm@xmission.com):
> > +This flag is intended for the implementation of control groups.
> 
> The above sentence is wrong.
> 
> +This flag is intended for the implementation of containers.
> 
> Would be correct.
> 
> Both control groups and namespaces feed into the user space container
> concept.  Control groups are multiprocess resource limits.
> Namespaces are affect the mapping from resource name to resource.
> 
> What is interesting is you can unshare a sysvipc namespace and still have
> sysvipc shared memory mapped from another sysvipc namespace.
> 
> This is something that needs to be watched for.

Oh, I see, so please disregard my last msg, it seems Eric was plenty
clear.

thanks,
-serge

  parent reply	other threads:[~2008-11-23 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 19:12 Michael Kerrisk
2008-11-20  1:16 ` Eric W. Biederman
2008-11-20  8:36   ` Cedric Le Goater
2008-11-20 11:28     ` Michael Kerrisk
2008-11-20 12:26       ` Cedric Le Goater
2008-11-20 16:28         ` Michael Kerrisk
2008-11-23 22:48   ` Serge E. Hallyn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-05  9:35 Michael Kerrisk
2007-08-05 12:24 ` Eric W. Biederman
2007-08-06  6:36   ` Michael Kerrisk

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=20081123224842.GD12687@hallyn.com \
    --to=serge@hallyn.com \
    --cc=clg@fr.ibm.com \
    --cc=dev@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@googlemail.com \
    --cc=xemul@openvz.org \
    --subject='Re: CLONE_NEWIPC documentation' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).