From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
Kirill Korotaev <dev-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Pavel Emelianov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
Quoting Eric W. Biederman (ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org):
> > +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
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
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
next prev parent reply other threads:[~2008-11-23 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 19:12 CLONE_NEWIPC documentation Michael Kerrisk
[not found] ` <4924651C.4080909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-11-20 1:16 ` Eric W. Biederman
2008-11-20 1:16 ` Eric W. Biederman
[not found] ` <m163mji4cz.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-11-20 8:36 ` Cedric Le Goater
2008-11-20 8:36 ` Cedric Le Goater
[not found] ` <49252174.7080709-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-20 11:28 ` Michael Kerrisk
2008-11-20 11:28 ` Michael Kerrisk
[not found] ` <cfd18e0f0811200328g643c1bdq46a48bac3a1ea744-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-20 12:26 ` Cedric Le Goater
2008-11-20 12:26 ` Cedric Le Goater
[not found] ` <4925575D.8060704-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-20 16:28 ` Michael Kerrisk
2008-11-20 16:28 ` Michael Kerrisk
2008-11-23 22:48 ` Serge E. Hallyn [this message]
2008-11-23 22:48 ` Serge E. Hallyn
-- 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-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
--cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=dev-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
--cc=xemul-GEFAQzZX7r8dnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.