From: matthltc@us.ibm.com
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Cc: Linux Containers <containers@lists.linux-foundation.org>
Subject: [RFC PATCH 0/4] Container Freezer: Reuse Suspend Freezer
Date: Thu, 03 Apr 2008 14:03:16 -0700 [thread overview]
Message-ID: <20080403210316.397506379@us.ibm.com> (raw)
NOTE: Due to problems with my MTA configuration two earlier attempts reached linux-pm
but not linux-kernel. Please cc linux-pm@lists.linux-foundation.org on replies.
This patchset is a prototype using the container infrastructure and
the swsusp freezer to freeze a group of tasks. I've merely taken Cedric's
patches, forward-ported them to 2.6.25-rc8-mm1 and done a small amount of
testing.
2 files are defined by the freezer subsystem in the container
filesystem :
* "freezer.freeze"
writing 1 will freeze all tasks and 0 unfreeze
reading will return the status of the freezer
* "freezer.kill"
writing <n> will send signal number <n> to all tasks
* Usage :
# mkdir /containers/freezer
# mount -t container -ofreezer freezer /containers/freezer
# mkdir /containers/freezer/0
# echo $some_pid > /containers/freezer/0/tasks
to get status of the freezer subsystem :
# cat /containers/freezer/0/freezer.freeze
RUNNING
to freeze all tasks in the container :
# echo 1 > /containers/freezer/0/freezer.freeze
# cat /containers/freezer/0/freezer.freeze
FREEZING
# cat /containers/freezer/0/freezer.freeze
FROZEN
to unfreeze all tasks in the container :
# echo 1 > /containers/freezer/0/freezer.freeze
# cat /containers/freezer/0/freezer.freeze
RUNNING
to kill all tasks in the container :
# echo 9 > /containers/freezer/0/freezer.kill
* Caveats:
- the FROZEN status is calculated and changed when the container
file "freezer.freeze" is read.
- frozen containers will be unfrozen when a system is resumed after
a suspend. This is addressed by the last patch.
* Series
Applies to 2.6.25-rc8-mm1
The first patches make the freezer available to all architectures
before implementing the freezer subsystem.
[RFC PATCH 1/4] Add TIF_FREEZE flag to all architectures
[RFC PATCH 2/4] Make refrigerator always available
[RFC PATCH 3/4] Implement freezer cgroup subsystem
[RFC PATCH 4/4] Skip frozen cgroups during power management resume
Each patch compiles, boots, and survives basic LTP containers and controllers
tests.
Comments are welcome.
Cheers,
-Matt Helsley
--
next reply other threads:[~2008-04-03 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 21:03 matthltc [this message]
2008-04-03 21:03 ` [RFC PATCH 1/4] Container Freezer: Add TIF_FREEZE flag to all architectures matthltc
2008-04-11 11:49 ` Pavel Machek
2008-04-03 21:03 ` [RFC PATCH 2/4] Container Freezer: Make refrigerator always available matthltc
2008-04-03 21:03 ` [RFC PATCH 3/4] Container Freezer: Implement freezer cgroup subsystem matthltc
2008-04-11 11:49 ` Pavel Machek
2008-04-03 21:03 ` [RFC PATCH 4/4] Container Freezer: Skip frozen cgroups during power management resume matthltc
2008-04-03 23:49 ` [Devel] [RFC PATCH 0/4] Container Freezer: Reuse Suspend Freezer Paul Menage
2008-04-04 3:03 ` Matt Helsley
2008-04-04 15:56 ` Oren Laadan
2008-04-04 22:27 ` Matt Helsley
2008-04-05 0:30 ` Oren Laadan
2008-04-05 0:54 ` Matt Helsley
2008-04-04 14:11 ` Serge E. Hallyn
2008-04-11 11:49 ` Pavel Machek
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=20080403210316.397506379@us.ibm.com \
--to=matthltc@us.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®