From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: legacy mode
Date: Thu, 27 Aug 2015 15:21:37 -0500 [thread overview]
Message-ID: <20150827202137.GA4221@mail.hallyn.com> (raw)
Hi,
after the unified cgroup overview at the containers mini-summit last week,
I mentioned the idea of supporting backward-compatible cgroupfs mounts in
the unified hierarchy.
The problem this would solve is running older userspace (i.e. libvirt in
a container running an older distro) on a newer kernel which has unified
hierarchy mounted.
I was thinking this could do the same tricks I'm doing in cgmanager to
support the existing cgmanager API with the unified hierarchy: i.e. create
a leaf node for every cgroup, and redirect any tasks written to the
cgroup.procs file for $cgroup to $cgroup/.leaf. I realize there will
likely be other changes, but keeping in mind that new unified-only features
aren't relevant for legacy support, maybe this sort of approach wouldn't
be as bad as I originally thought it would be. Not supporting release-agent
is also a non-issue imo.
The combination of cgroup namespaces, a "legacy-mount" mode, and fully
proper hierarchical support leading to full safe delegation, would
allow cgmanager and lxcfs to be killed with extreme privilege - WIN!
So is anyone interested on working on a legacy mount option? What other
issues need to be considered there?
thanks,
-serge
next reply other threads:[~2015-08-27 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 20:21 Serge E. Hallyn [this message]
[not found] ` <20150827202137.GA4221-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2015-08-27 20:27 ` legacy mode Tejun Heo
[not found] ` <20150827202722.GH26785-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2015-08-27 20:45 ` Serge E. Hallyn
[not found] ` <20150827204500.GA4447-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2015-08-27 20:48 ` Tejun Heo
[not found] ` <20150827204825.GI26785-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2015-08-27 21:23 ` Serge E. Hallyn
2015-08-31 22:36 ` Eric W. Biederman
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=20150827202137.GA4221@mail.hallyn.com \
--to=serge-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+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.