[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47A1F2DB.7080600@fr.ibm.com>
Date: Thu, 31 Jan 2008 17:10:03 +0100
From: Cedric Le Goater <clg@...ibm.com>
To: Kirill Korotaev <dev@...ru>
CC: Pierre Peiffer <pierre.peiffer@...l.net>,
containers@...ts.linux-foundation.org,
Alexey Dobriyan <adobriyan@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.24-rc8-mm1 09/15] (RFC) IPC: new kernel API to change
an ID
Hello Kirill !
Kirill Korotaev wrote:
> Pierre,
>
> my point is that after you've added interface "set IPCID", you'll need more and more for checkpointing:
> - "create/setup conntrack" (otherwise connections get dropped),
> - "set task start time" (needed for Oracle checkpointing BTW),
> - "set some statistics counters (e.g. networking or taskstats)"
> - "restore inotify"
> and so on and so forth.
right. we know that we will have to handle a lot of these
and more and we will need an API for it :) so how should we
handle it ?
through a dedicated syscall that would be able to checkpoint
and/or restart a process, an ipc object, an ipc namespace, a
full container ? will it take a fd or a big binary blob ?
I personally really liked Pavel idea's of filesystem. but we
dropped the thread.
that's for the user API but we will need also kernel services
to expose (checkpoint) states and restore them. If it's too
early to talk about the user API, we could try first to refactor
the kernel internals to expose correctly what we need.
That's what Pierre's patchset is trying to do.
Cheers,
C.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists