Linux Container Development
 help / color / mirror / Atom feed
From: Aristeu Rozanski <aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Kay Sievers <kay.sievers-tD+1rO4QERM@public.gmane.org>,
	Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
	Lennart Poettering
	<lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org>,
	Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH cgroup/for-3.11] cgroup: disallow rename(2) if sane_behavior
Date: Mon, 17 Jun 2013 09:00:29 -0400	[thread overview]
Message-ID: <20130617130029.GB3212@redhat.com> (raw)
In-Reply-To: <20130616221556.GC28587-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>

On Sun, Jun 16, 2013 at 03:15:56PM -0700, Tejun Heo wrote:
> Li is working to make cpuset composable.  As for device_cgroup, I'm
> not sure what to do.  Aristeu, I know you already put in too much work
> into devcg and I'm sorry that I'm raising this now but would you be
> interested in tackling this too?

sure, I'm on it. that sounds like one of the versions of the hierarchy
patchset - having the local configuration saved but only applying what's
possible based on parent's state.

-- 
Aristeu

  parent reply	other threads:[~2013-06-17 13:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14  3:47 [PATCH cgroup/for-3.11] cgroup: disallow rename(2) if sane_behavior Tejun Heo
     [not found] ` <20130614034717.GA31533-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-06-14  7:44   ` Li Zefan
2013-06-14 18:18   ` [PATCH v2 " Tejun Heo
     [not found]     ` <20130614181822.GC6593-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-06-18  9:11       ` Li Zefan
2013-06-18 15:16       ` Tejun Heo
2013-06-16  7:16   ` [PATCH " Lennart Poettering
     [not found] ` <20130616071648.GA1978@tango.0pointer.de>
     [not found]   ` <20130616071648.GA1978-kS5D54t9nk0aINubkmmoJbNAH6kLmebB@public.gmane.org>
2013-06-16 22:15     ` Tejun Heo
     [not found]       ` <20130616221556.GC28587-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-06-17 13:00         ` Aristeu Rozanski [this message]
     [not found]           ` <20130617130029.GB3212-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-06-17 17:06             ` Tejun Heo
2013-06-17 13:51         ` Michal Hocko
2013-06-17 16:33         ` Lennart Poettering
     [not found]       ` <20130617135122.GD5018@dhcp22.suse.cz>
     [not found]         ` <20130617135122.GD5018-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-06-17 16:51           ` Tejun Heo
     [not found]             ` <20130617165129.GA32663-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-06-21  8:35               ` Michal Hocko
     [not found]       ` <20130617163353.GD22846@tango.0pointer.de>
     [not found]         ` <20130617163353.GD22846-kS5D54t9nk0aINubkmmoJbNAH6kLmebB@public.gmane.org>
2013-06-17 16:53           ` Tejun Heo

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=20130617130029.GB3212@redhat.com \
    --to=aris-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
    --cc=kay.sievers-tD+1rO4QERM@public.gmane.org \
    --cc=lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org \
    --cc=mhocko-AlSwsSmVLrQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox