On Wed, 26 Nov 2008 10:42:39 +0300 Evgeniy Polyakov [EMAIL PROTECTED] wrote:
Hi Andrew.
On Tue, Nov 25, 2008 at 04:24:34PM -0800, Andrew Morton ([EMAIL PROTECTED])
wrote:
I guess I'm being more than usually thick, but I don't understand what
this is all about, why it was implemented,
On Wed, Nov 26, 2008 at 12:15:38AM -0800, Andrew Morton ([EMAIL PROTECTED])
wrote:
OK, so we have a super-duper framework which will allow us to add pids
(and other things) to inotify messages.
Yup :)
This still doesn't provide a reason for anyone to be interested in the
code! Why do we
Document /proc/timer_list ABI.
This documents all of /timer_list, including the extension
adding jiffie timers, as proposed in the patch:
[PATCH] Display active jiffie timers in /proc/timer_list, v2
Signed-off-by: Joe Korty [EMAIL PROTECTED]
Index:
Checkpoint-restart (c/r): fixes a couple of bugs and a DoS issue
(tested against v2.6.28-rc3).
We'd like these to make it into -mm. This version addresses the
last of the known bugs. Please pull at least the first 11 patches,
as they are similar to before.
Patches 1-11 are stable, providing
Now we can do external checkpoint, i.e. act on another task.
sys_checkpoint() now looks up the target pid (in our namespace) and
checkpoints that corresponding task. That task should be the root of
a container.
sys_restart() remains the same, as the restart is always done in the
context of the
Covers application checkpoint/restart, overall design, interfaces,
usage, shared objects, and and checkpoint image format.
Changelog[v8]:
- Split into multiple files in Documentation/checkpoint/...
- Extend documentation, fix typos and comments from feedback
Signed-off-by: Oren Laadan [EMAIL
Add those interfaces, as well as helpers needed to easily manage the
file format. The code is roughly broken out as follows:
checkpoint/sys.c - user/kernel data transfer, as well as setup of the
CR context (a per-checkpoint data structure for housekeeping)
checkpoint/checkpoint.c - output
