From: Matt Helsley <matthltc@us.ibm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Paul Menage <menage@google.com>, Pavel Machek <pavel@ucw.cz>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
linux-pm@lists.linux-foundation.org,
Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH 0/4] Container Freezer: Reuse Suspend Freezer
Date: Mon, 07 Jul 2008 16:02:24 -0700 [thread overview]
Message-ID: <1215471744.9023.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20080707225823.502032693@us.ibm.com>
On Mon, 2008-07-07 at 15:58 -0700, Matt Helsley wrote:
> This patchset reuses the container infrastructure and the swsusp freezer to
> freeze a group of tasks.
>
> The freezer subsystem in the container filesystem defines a file named
> freezer.state. Writing "FROZEN" to the state file will freeze all tasks in the
> cgroup. Subsequently writing "RUNNING" will unfreeze the tasks in the cgroup.
> Reading will return the current state.
>
> * Examples of usage :
>
> # mkdir /containers/freezer
> # mount -t cgroup -ofreezer,signal freezer /containers
> # mkdir /containers/0
> # echo $some_pid > /containers/0/tasks
>
> to get status of the freezer subsystem :
>
> # cat /containers/0/freezer.state
> RUNNING
>
> to freeze all tasks in the container :
>
> # echo FROZEN > /containers/0/freezer.state
> # cat /containers/0/freezer.state
> FREEZING
> # cat /containers/0/freezer.state
> FROZEN
>
> to unfreeze all tasks in the container :
>
> # echo RUNNING > /containers/0/freezer.state
> # cat /containers/0/freezer.state
> RUNNING
>
> to kill all tasks in the container :
>
> # echo 9 > /containers/0/signal.kill
>
> I've reworked Cedric's patches to use task_lock() to protect access to the
> task's cgroup.
>
> Paul, Pavel asked me to send these to Rafael next. They are patches to make
> the freezer useful for checkpoint/restart using cgroups so it would be nice
> to get an explicit [N]Ack from you first.
>
> Rafael, if Paul agrees, please consider applying these patches.
>
> Changes since v3:
> v4 (Almost all of these changes are confined to patch 3):
> Reworked the series to use task_lock() instead of RCU.
> Reworked the series to use write_string() and read_seq_string()
> cgroup methods.
FYI - This means these patches need Paul's patches introducing
write_string(). I can certainly restore the old code for .read
and .write, but I was anticipating write_string() making it into various
trees first. If that's not necessarily the case please let me know.
Cheers,
-Matt
next prev parent reply other threads:[~2008-07-07 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 22:58 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 ` Matt Helsley [this message]
2008-07-08 3:31 ` [PATCH 0/4] Container Freezer: Reuse Suspend Freezer 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
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=1215471744.9023.14.camel@localhost.localdomain \
--to=matthltc@us.ibm.com \
--cc=containers@lists.linux-foundation.org \
--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
Powered by JetHome