From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: legacy mode
Date: Thu, 27 Aug 2015 16:23:26 -0500 [thread overview]
Message-ID: <20150827212326.GA5019@mail.hallyn.com> (raw)
In-Reply-To: <20150827204825.GI26785-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
On Thu, Aug 27, 2015 at 04:48:25PM -0400, Tejun Heo wrote:
> Hello, Serge.
>
> On Thu, Aug 27, 2015 at 03:45:00PM -0500, Serge E. Hallyn wrote:
> > > If the legacy userspace doesn't do any resource control, the leaf rule
> > > restriction doesn't apply anyway, so nothing to worry about.
> >
> > My main use case is nested lxc, presumably with systemd inside some of
> > the nested containers, so this would definately be an issue.
>
> W/o controllers in the nested environment, it should be fine. W/
> controllers, I don't think this is going to fly. I don't think trying
> to bridge the two versions is a healthy direction in the long term.
That's unfortunate as it suggests that lxcfs is the only way around
this problem :(
next prev parent reply other threads:[~2015-08-27 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 20:21 legacy mode Serge E. Hallyn
[not found] ` <20150827202137.GA4221-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2015-08-27 20:27 ` 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 [this message]
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=20150827212326.GA5019@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.