From: Pierre Peiffer <pierre.peiffer@bull.net>
To: Michael Kerrisk <mtk.linux.lists@gmail.com>
Cc: linux-kernel@vger.kernel.org, containers@lists.osdl.org,
mtk-manpages@gmx.net
Subject: Re: [RFC][PATCH 0/2] New API to change the IDs of an existing IPC
Date: Mon, 01 Oct 2007 09:19:18 +0200 [thread overview]
Message-ID: <47009F76.9050802@bull.net> (raw)
In-Reply-To: <517f3f820709292330i56caf106yfa18778d741f8e1a@mail.gmail.com>
Michael Kerrisk a écrit :
> Hi Pierre,
>
>> As I'm seeing some discussion/interest about IPC, I would like to propose
>> these patches, which provide an easy way to change the ID of an exiting IPC.
>> This work is done around the checkpoint/restart of applications. In the case of
>> the IPCs, we need (among others) this functionality.
>
> Can you give some more detailed explanation of why this
> functionaility is needed.
Sure; in the case of the checkpoint/restart, when you restart an application, what you want is to recreate all system ressources with the same properties they had, when you have checkpointed it.
For IPCs, this means that you need to recreate all the IPCs with the same IDs (at least).
For now, this ID is computed by the system when an IPC is created and you can't specify or modify it.
These patches give you the possibility of changing this ID once the IPC is created.
--
Pierre Peiffer
prev parent reply other threads:[~2007-10-01 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 14:58 [RFC][PATCH 0/2] New API to change the IDs of an existing IPC Pierre Peiffer
2007-09-30 6:30 ` Michael Kerrisk
2007-10-01 7:19 ` Pierre Peiffer [this message]
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=47009F76.9050802@bull.net \
--to=pierre.peiffer@bull.net \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=mtk.linux.lists@gmail.com \
/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