From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: CGroup Namespaces (v4) Date: Mon, 16 Nov 2015 17:37:58 -0500 Message-ID: <20151116223758.GM18894@mtj.duckdns.org> References: <1447703505-29672-1-git-send-email-serge@hallyn.com> <20151116204606.GA30681@mail.hallyn.com> <564A41AF.4040208@nod.at> <20151116205452.GA30975@mail.hallyn.com> <87y4dxh9b8.fsf@x220.int.ebiederm.org> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=F7CjGHldgXdfUYHqWfdgmtBKTkeJDodJsVAhOnYQ8cY=; b=gH7BVZQjz4zPJd9mCu1GwvW6+9mdH0czx9LgQqoJ4jCCFalBD4ZB8mov/H1xGDz2wz 5iL0OT3aU4dyNjN7fBTSXs+SHpq7igHmioUyMGxwFsjFNkcKhONkLZFsPxxqX+PrhrtC Y65TzpF2/nXwnR3wQEjLizIt0zoUxzIbSqj7JPN05Hn/ganJ3m5Q0EIeKZniX6uzCmD9 +tWMK9iLgAYZrqf5HxdE6pahEs44J7HGGbor8PgO501yP1Qexxc+yRIABI73mDU09eXa tmpJzAX8J0t35/APCBzMitGInvpBfbcwoMbgK4M8l6K4ugR/CqovTZNjPamE/AxFX88r Z/gA== Content-Disposition: inline In-Reply-To: <87y4dxh9b8.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Eric W. Biederman" Cc: "Serge E. Hallyn" , Richard Weinberger , Richard Weinberger , LKML , "open list:ABI/API" , Linux Containers , LXC development mailing-list , cgroups mailinglist , Andrew Morton Hello, Eric. On Mon, Nov 16, 2015 at 04:24:27PM -0600, Eric W. Biederman wrote: > Does this allow mixing of cgroupfs and cgroupfs2? That is can I: "mount > -t cgroupfs" inside a container and "mount -t cgroupfs2" outside a > container? and still have reasonable things happen? I suspect the > semantics of cgroups prevent this but I am interested to know what happens. cgroup v1 and v2 are just separate hierarchies. They can't nest each other but co-existing and namespacing on their own is completely fine. The caveat is that a given controller can be on only one hierarchy but that's the same among v1 hierarchies too. Thanks. -- tejun