public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Helsley <matthltc@us.ibm.com>
To: Paul Menage <menage@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Cedric Le Goater <clg@fr.ibm.com>,
	Linux Containers <containers@lists.linux-foundation.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>,
	linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH 0/4] Container Freezer: Reuse Suspend Freezer
Date: Wed, 09 Jul 2008 14:58:43 -0700	[thread overview]
Message-ID: <1215640723.7149.35.camel@localhost.localdomain> (raw)
In-Reply-To: <6599ad830807081307j811689aldf0f6cb38579c450@mail.gmail.com>


On Tue, 2008-07-08 at 13:07 -0700, Paul Menage wrote:
> On Tue, Jul 8, 2008 at 1:06 PM, Paul Menage <menage@google.com> wrote:
> > On Tue, Jul 8, 2008 at 12:39 PM, Matt Helsley <matthltc@us.ibm.com> wrote:
> >>
> >> One is to try and disallow users from moving frozen tasks. That doesn't
> >> seem like a good approach since it would require a new cgroups interface
> >> "can_detach()".
> >
> > Detaching from the old cgroup happens at the same time as attaching to
> > the new cgroup, so can_attach() would work here.

Update: I've made a patch implementing this. However it might be better
to just modify attach() to thaw the moving task rather than disallow
moving the frozen task. Serge, Cedric, Kame-san, do you have any
thoughts on which is more useful and/or intuitive?

> And the whole can_attach()/attach() protocol needs reworking anyway,
> see my email (hopefully) later today.
> 
> Paul

Interesting. I look forward to seeing this.

Cheers,
	-Matt


  reply	other threads:[~2008-07-09 21:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 22:58 [PATCH 0/4] Container Freezer: Reuse Suspend Freezer Matt Helsley
2008-07-07 22:58 ` [PATCH 1/4] Container Freezer: Add TIF_FREEZE flag to all architectures Matt Helsley
2008-07-07 22:58 ` [PATCH 2/4] Container Freezer: Make refrigerator always available Matt Helsley
2008-07-09 19:21   ` Serge E. Hallyn
2008-07-07 22:58 ` [PATCH 3/4] Container Freezer: Implement freezer cgroup subsystem Matt Helsley
2008-07-07 22:58 ` [PATCH 4/4] Container Freezer: Skip frozen cgroups during power management resume Matt Helsley
2008-07-07 23:02 ` [PATCH 0/4] Container Freezer: Reuse Suspend Freezer Matt Helsley
2008-07-08  3:31 ` KAMEZAWA Hiroyuki
2008-07-08 19:39   ` Matt Helsley
2008-07-08 20:06     ` Paul Menage
2008-07-08 20:07       ` Paul Menage
2008-07-09 21:58         ` Matt Helsley [this message]
2008-07-10  0:42           ` KAMEZAWA Hiroyuki
2008-07-10  2:18             ` [RFC][PATCH] Container Freezer: Don't Let Frozen Stuff Change Matt Helsley
2008-07-10  3:20               ` Li Zefan
2008-07-11 23:51                 ` Matt Helsley
2008-07-10 14:40             ` [PATCH 0/4] Container Freezer: Reuse Suspend Freezer Serge E. Hallyn
  -- strict thread matches above, loose matches on Subject: below --
2008-06-24 13:58 [patch " Matt Helsley
     [not found] <20080403001529.052250759@us.ibm.com>
2008-04-03  0:19 ` [PATCH " Matt Helsley

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=1215640723.7149.35.camel@localhost.localdomain \
    --to=matthltc@us.ibm.com \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=menage@google.com \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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