.
Note: I've integrated in this patch a patch sent by Suka last week, that
defines ns_of_pid() (see http://lkml.org/lkml/2008/11/25/460)
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/pid.h | 11 +++
ipc/mqueue.c| 12 +++-
2 files changed, 22
(task_active_pid_ns);
+
/*
* Used by proc to find the first pid that is greater then or equal to nr.
*
--
Nadia Derbey [EMAIL PROTECTED]
___
Containers mailing list
[EMAIL PROTECTED]
https://lists.linux-foundation.org/mailman/listinfo/containers
Eric W. Biederman wrote:
[EMAIL PROTECTED] writes:
[PATCH 05/05]
This patch uses the value written into the next_syscall_data proc file
as a target file descriptor for the next file to be opened.
This makes it easy to restart a process with the same fds as the ones it was
using during the
Pavel Machek wrote:
On Tue 2008-07-08 16:47:21, Serge E. Hallyn wrote:
Quoting Pavel Machek ([EMAIL PROTECTED]):
Hi!
An alternative to this solution consists in defining a new field in the
task structure (let's call it next_syscall_data) that, if set, would
change
the behavior of next
Pavel Machek wrote:
Hi!
An alternative to this solution consists in defining a new field in the
task structure (let's call it next_syscall_data) that, if set, would change
the behavior of next syscall to be called. The sys_fork_with_id() previously
cited can be replaced by
1) set
Serge E. Hallyn wrote:
Quoting Pavel Machek ([EMAIL PROTECTED]):
An alternative to this solution consists in defining a new field in the
task structure (let's call it next_syscall_data) that, if set, would
change
the behavior of next syscall to be called. The sys_fork_with_id()
previously
Eric W. Biederman wrote:
[EMAIL PROTECTED] writes:
[PATCH 03/05]
This patch uses the value written into the next_syscall_data proc file
as a target upid nr for the next process to be created.
The following syscalls have a new behavior if next_syscall_data is set:
. fork()
. vfork()
. clone()
Paul Menage wrote:
On Thu, Jul 10, 2008 at 12:58 AM, Nadia Derbey [EMAIL PROTECTED] wrote:
Actually, what I've started working on these days is replace the proc
interface by a syscall to set the next_syscall_data field: I think this
might help us avoid defining a precise list of the new
'ing
the open file descriptor.
The following syscalls are impacted if next_syscall_data is set:
. open()
. openat()
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/open.c | 62 +-
1 file changed, 61 insertions(+), 1 deletion
Resending after fixing the issues pointed out by Serge.
Also ported to 2.6.26-rc8-mm1.
Regards,
Nadia
--
This patchset is a part of an effort to change some syscalls behavior for
checkpoint restart.
When restarting an object that has previously been checkpointed, its state
should
-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/next_syscall_data.h | 12
ipc/msg.c | 19 ++-
ipc/sem.c | 16 +++-
ipc/shm.c | 19 ++-
4 files changed, 63
the syscalls to have a non-default behavior.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/exec.c |6 +
fs/proc/base.c| 75 ++
include/linux/next_syscall_data.h | 32
include/linux/sched.h |6
to nested namespaces, only
the upper namespace level upid nr is allowed to be predefined, since there
is not yet a way to take a snapshot of upid nrs at all namespaces levels.
But this can easily be extended in the future.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux
.
This is particularly useful when restarting an application, as we need
sometimes the syscalls to have a non-default behavior.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/exec.c |6 +
fs/proc/base.c| 75 ++
include/linux
()
. semget()
. shmget()
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/next_syscall_data.h | 17 +++--
ipc/util.c| 38
++
2 files changed, 45 insertions(+), 10 deletions(-)
Index: linux-2.6.26-rc5-mm3
point, we will want to discuss the right way to dump that data. Do
we add a new file under /proc/pid, use /proc/pid/status, or find some
other way?
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/next_syscall_data.h |2
include/linux/pid.h |2
kernel
Pavel Machek wrote:
Hi!
This patchset is a part of an effort to change some syscalls behavior for
checkpoint restart.
When restarting an object that has previously been checkpointed, its state
should be unchanged compared to the checkpointed image.
For example, a restarted process should
to nested namespaces, only
the upper namespace level upid nr is allowed to be predefined, since there
is not yet a way to take a snapshot of upid nrs at all namespaces levels.
But this can easily be extended in the future.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux
-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/next_syscall_data.h | 12 +++-
ipc/msg.c | 19 ++-
ipc/sem.c | 16 +++-
ipc/shm.c | 19 ++-
4 files changed, 62
'ing
the open file descriptor.
The following syscalls are impacted if next_syscall_data is set:
. open()
. openat()
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/open.c | 58 +-
1 file changed, 57 insertions(+), 1 deletion
[PATCH 02/05]
This patch uses the value written into the next_syscall_data proc file
as a target id for the next IPC object to be created.
The following syscalls have a new behavior if next_syscall_data is set:
. mssget()
. semget()
. shmget()
Signed-off-by: Nadia Derbey [EMAIL PROTECTED
This patchset is a part of an effort to change some syscalls behavior for
checkpoint restart.
When restarting an object that has previously been checkpointed, its state
should be unchanged compared to the checkpointed image.
For example, a restarted process should have the same upid nr as the
Serge E. Hallyn wrote:
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
PATCH [06/06]
This patch introduces the .write seq operation for /proc/pid/semundo.
In order to simplify the locking strategy, the write operation is only allowed
to 'current'.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED
[ PATCH 01/01 ]
This is a trivial patch that correctly closes the semundo file after restoring
the semundo list.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
cr.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: cryo-001/cr.c
Serge E. Hallyn wrote:
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
PATCH [06/06]
This patch introduces the .write seq operation for /proc/pid/semundo.
In order to simplify the locking strategy, the write operation is only allowed
to 'current'.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED
, tell me if I need to resend the complete series.
Regards,
Nadia
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
Documentation/filesystems/proc.txt | 56 +++--
1 file changed, 54 insertions(+), 2 deletions(-)
Index: linux-2.6.26-rc5-mm3.4.semundo/Documentation
) {
/* section where undo_list can be used quietly */
...
}
...
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sem.h |4 +++-
ipc/sem.c | 22 ++
2 files changed, 21
PATCH [05/06]
This patch introduces the .show seq operation for /proc/pid/semundo.
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
ipc/sem.c | 28
1 file changed, 28 insertions(+)
Index: linux-2.6.26-rc5-mm3/ipc
PATCH [03/06]
This patch introduces the .start and .stop seq operations for
/proc/pid/semundo.
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
ipc/sem.c | 43 +--
1 file changed, 41 insertions(+), 2
[EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c |3 +
fs/proc/internal.h |1
ipc/sem.c | 127 +++--
3 files changed, 128 insertions(+), 3 deletions(-)
Index: linux-2.6.26-rc5-mm3/fs/proc/base.c
PATCH [06/06]
This patch introduces the .write seq operation for /proc/pid/semundo.
In order to simplify the locking strategy, the write operation is only allowed
to 'current'.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c |2
ipc/sem.c | 250
This patchset is a part of an effort to make sysv ipc objects
read/writable from userspace for checkpoint / restart.
System V ipc's are objects that are global to a system and can thus be
checkpointed and restarted on a container basis. But some parts of the ipc
structures are process related
of the whole list. But, oth, this reduces the
the performance impact on the access to the undo_list.
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
ipc/sem.c | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
Index: linux
to the undo_list.
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
Acked-by: Serge Hallyn [EMAIL PROTECTED]
---
ipc/sem.c | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
Index: linux-2.6.26-rc5-mm3/ipc/sem.c
Documentation/filesystems/proc.txt
Ok, will do that.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c |2
ipc/sem.c | 250
-
2 files changed, 250 insertions(+), 2 deletions(-)
Index: linux-2.6.26-rc5-mm3/fs
Hi,
A couple of months ago, Pierre Peiffer has submitted a patch series to enable
checkpointing / restarting ipcs.
4 of these patches were related to semaphores:
https://lists.linux-foundation.org/pipermail/containers/2008-January/thread.html#9756
();
...
if (undo_list ret) {
/* section where undo_list can be used quietly */
...
}
...
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sem.h |5 -
ipc/sem.c
corresponding to each semaphores of the semaphores array.
This interface will be particularly useful to allow a user access
these data, for example for checkpointing a process
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c |3
.
The operation failes if the given semaphore ID does not exist or if the
number of values does not match the number of semaphores in the array.
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c |2
include/linux/sem.h
them work on a specified
task, passed in parameter, instead of current.
This is mainly a preparation for the semundo_write() operation, on the
/proc/pid/semundo file, as provided in the next patch.
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Signed-off-by: Nadia Derbey [EMAIL PROTECTED
Serge E. Hallyn wrote:
Quoting Nadia Derbey ([EMAIL PROTECTED]):
Cedric Le Goater wrote:
Looks like it has worked for me (msg1 creates 1000 msg queues, sleeps
for a while and then removes the msg queues).
cool. which kernel are you using ?
C.
2.6.25-mm1 (sorry for the late answer
Luck, Tony wrote:
Well, this printk had been suggested by somebody (sorry I don't remember
who) when I first submitted the patch. Actually I think it might be
useful for a sysadmin to be aware of a change in the msgmni value: we
have the message not only at boot time, but also each time msgmni
Serge E. Hallyn wrote:
Quoting Luck, Tony ([EMAIL PROTECTED]):
Well, this printk had been suggested by somebody (sorry I don't remember
who) when I first submitted the patch. Actually I think it might be
useful for a sysadmin to be aware of a change in the msgmni value: we
have the message
Cedric Le Goater wrote:
Looks like it has worked for me (msg1 creates 1000 msg queues, sleeps
for a while and then removes the msg queues).
cool. which kernel are you using ?
C.
2.6.25-mm1 (sorry for the late answer - plenty of days off in France in
May).
Regards,
Nadia
Tony Luck wrote:
On Mon, Feb 11, 2008 at 7:16 AM, [EMAIL PROTECTED] wrote:
Index: linux-2.6.24-mm1/ipc/msg.c
===
--- linux-2.6.24-mm1.orig/ipc/msg.c 2008-02-07 15:02:29.0 +0100
+++ linux-2.6.24-mm1/ipc/msg.c
Cedric Le Goater wrote:
Dave Hansen wrote:
A guy named Marc Vertes wrote this as a little demonstration of
checkpoint/restart. I've been using it to experiment with
checkpoint/restart. I thought it might be of some use as we move
subsystems to being helped by the kernel to checkpoint and
.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/exec.c |3 +
fs/proc/base.c | 76 +++
include/linux/sched.h |3 +
include/linux/sysids.h | 24 +
kernel/Makefile|2 -
kernel/exit.c |4
[PATCH 03/04]
This patch makes use of the target id specified by a previous write into
/proc/self/task/tid/next_id as the id to use to allocate the next IPC
object.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sysids.h |7 +++
ipc/util.c | 41
set as follows
(say it is forked in a pid ns of level L):
level upid nr
L -- X0
..
L - i -- Xi
..
L - n + 1 -- Xn-1
Then, for levels L-n down to level 0, the pids will be left to the kernel
choice.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sysids.h
When restarting a process that has been previously checkpointed, that process
should keep on using some of its ids (such as its process id, or sysV ipc ids).
This patch provides a feature that can help ensuring this saved state reuse:
it makes it possible to create an object with a pre-defined
[PATCH 04/04]
This patch makes use of the target ids specified by a previous write to
/proc/self/task/tid/next_id as the ids to use to allocate the next upid nrs.
Upper levels upid nrs that are not specified in next_pids file are left to the
kernel choice.
Signed-off-by: Nadia Derbey [EMAIL
Nick Andrew wrote:
On Fri, Apr 04, 2008 at 04:51:29PM +0200, [EMAIL PROTECTED] wrote:
. echo LONG XX /proc/self/next_id
next object to be created will have an id set to XX
. echo LONGn X0 ... Xn-1 /proc/self/next_id
next object to be created will have its ids set to XX0, ...
-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/exec.c |3 +
fs/proc/base.c | 73 +
include/linux/sched.h |3 +
include/linux/sysids.h | 24 +
kernel/Makefile|2 -
kernel/exit.c |4 ++
kernel
Hi,
When restarting a process that has been previously checkpointed, that process
should keep on using some of its ids (such as its process id, or sysV ipc ids).
This patch provides a feature that can help ensuring this saved state reuse:
it makes it possible to create an object with a
[PATCH 03/04]
This patch makes use of the target id specified by a previous write into
/proc/self/next_id as the id to use to allocate the next IPC object.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sysids.h |7 +++
ipc/util.c | 40
[PATCH 04/04]
This patch makes use of the target ids specified by a previous write to
/proc/self/next_id as the ids to use to allocate the next upid nrs.
Upper levels upid nrs that are not specified in next_pids file are left to the
kernel choice.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED
as follows
(say it is forked in a pid ns of level L):
level upid nr
L -- X0
..
L - i -- Xi
..
L - n + 1 -- Xn-1
Then, for levels L-n down to level 0, the pids will be left to the kernel
choice.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sysids.h | 27
Hi,
Here is a second version of what has been proposed 2 weeks ago to create
an object with a pre-defined id (this feature would be used during the
restart operation) - see thread
https://lists.linux-foundation.org/pipermail/containers/2008-March/thread.html#10287
Main changes since last
[PATCH 03/04]
This patch makes use of the target id specified by a previous write into
/proc/self/next_id as the id to use to allocate the next IPC object.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sysids.h |7 +++
ipc/util.c | 39
[PATCH 04/04]
This patch makes use of the target ids specified by a previous write to
/proc/self/next_id as the ids to use to allocate the next upid nrs.
Upper levels upid nrs that are not specified in next_pids file are left to the
kernel choice.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED
as follows
(say it is forked in a pid ns of level L):
level upid nr
L -- X0
..
L - i -- Xi
..
L - n + 1 -- Xn-1
Then, for levels L-n down to level 0, the pids will be left to the kernel
choice.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/sysids.h | 27
-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c | 73 +
include/linux/sched.h |3 ++
include/linux/sysids.h | 18
kernel/Makefile|2 -
kernel/fork.c |2 +
kernel/nextid.c| 69
Oren Laadan wrote:
Nadia Derbey wrote:
Oren Laadan wrote:
[EMAIL PROTECTED] wrote:
A couple of weeks ago, a discussion has started after Pierre's
proposal for
a new syscall to change an ipc id (see thread
http://lkml.org/lkml/2008/1/29/209).
Oren's suggestion was to force
Pavel Emelyanov wrote:
Oren Laadan wrote:
Nadia Derbey wrote:
Oren Laadan wrote:
[EMAIL PROTECTED] wrote:
A couple of weeks ago, a discussion has started after Pierre's
proposal for
a new syscall to change an ipc id (see thread
http://lkml.org/lkml/2008/1/29/209).
Oren's suggestion
Pavel Emelyanov wrote:
[EMAIL PROTECTED] wrote:
@@ -122,14 +122,26 @@ static void free_pidmap(struct upid *upi
atomic_inc(map-nr_free);
}
-static int alloc_pidmap(struct pid_namespace *pid_ns)
+static int alloc_pidmap(struct pid_namespace *pid_ns, struct pid_list *pid_l,
+
Pavel Emelyanov wrote:
Nadia Derbey wrote:
Pavel Emelyanov wrote:
[EMAIL PROTECTED] wrote:
@@ -122,14 +122,26 @@ static void free_pidmap(struct upid *upi
atomic_inc(map-nr_free);
}
-static int alloc_pidmap(struct pid_namespace *pid_ns)
+static int alloc_pidmap(struct pid_namespace
A couple of weeks ago, a discussion has started after Pierre's proposal for
a new syscall to change an ipc id (see thread
http://lkml.org/lkml/2008/1/29/209).
Oren's suggestion was to force an object's id during its creation, rather
than 1. create it, 2. change its id.
So here is an
[PATCH 01/04]
This patch proposes the procfs facilities needed to feed the id for the
next ipc object to be allocated.
if an
echo XX /proc/self/next_ipcid
is issued, next ipc object to be created will have XX as its id.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c
[PATCH 03/04]
This patch makes use of the target id specified by a previous write into
/proc/self/next_ipcid as the id to use to allocate the next IPC object.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
ipc/util.c | 39 +++
1 file changed, 31
as follows
(say it is forked in a pid ns of level L):
level upid nr
L -- X0
..
L - i -- Xi
..
L - n + 1 -- Xn-1
Then, for levels L-n down to level 0, the pids will be left to the kernel
choice.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
fs/proc/base.c | 74
[PATCH 04/04]
This patch makes use of the target ids specified by a previous write to
/proc/self/next_pids as the ids to use to allocate the next upid nrs.
Upper levels upid nrs that are not specified in next_pids file are left to the
kernel choice.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED
Matt Helsley wrote:
On Tue, 2008-02-19 at 18:16 +0100, Nadia Derbey wrote:
snip
+#define MAX_MSGQUEUES 16 /* MSGMNI as defined in linux/msg.h */
+
It's not quite the maximum anymore, is it? More like the minumum
maximum ;). A better name might better document what the test
Subrata Modak wrote:
Nadia Derbey wrote:
Andrew Morton wrote:
On Mon, 11 Feb 2008 15:16:47 +0100 [EMAIL PROTECTED] wrote:
[PATCH 01/08]
This patch computes msg_ctlmni to make it scale with the amount of
lowmem.
msg_ctlmni is now set to make the message queues occupy 1/32
Nadia Derbey wrote:
Andrew Morton wrote:
On Mon, 11 Feb 2008 15:16:47 +0100 [EMAIL PROTECTED] wrote:
[PATCH 01/08]
This patch computes msg_ctlmni to make it scale with the amount of
lowmem.
msg_ctlmni is now set to make the message queues occupy 1/32 of the
available
lowmem.
Some
Andrew Morton wrote:
On Tue, 12 Feb 2008 16:15:00 +0100
Nadia Derbey [EMAIL PROTECTED] wrote:
Andrew Morton wrote:
On Tue, 12 Feb 2008 10:32:31 +0100 Nadia Derbey [EMAIL PROTECTED] wrote:
it builds fine, modulo some changes in ipv4 and ipv6 (see attached patch
- didn't find
Andrew Morton wrote:
On Mon, 11 Feb 2008 15:16:53 +0100
[EMAIL PROTECTED] wrote:
[PATCH 07/08]
This patch makes msgmni not recomputed anymore upon ipc namespace creation /
removal or memory add/remove, as soon as it has been set from userland.
As soon as msgmni is explicitely set via procfs
Nadia Derbey wrote:
Andrew Morton wrote:
On Mon, 11 Feb 2008 15:16:53 +0100
[EMAIL PROTECTED] wrote:
[PATCH 07/08]
This patch makes msgmni not recomputed anymore upon ipc namespace
creation /
removal or memory add/remove, as soon as it has been set from userland.
As soon as msgmni
Andrew Morton wrote:
On Tue, 12 Feb 2008 10:32:31 +0100 Nadia Derbey [EMAIL PROTECTED] wrote:
it builds fine, modulo some changes in ipv4 and ipv6 (see attached patch
- didn't find it in the hot fixes).
OK, thanks for checking. Did you confirm that we don't have unneeded code
in vmlinux
Andrew Morton wrote:
On Mon, 11 Feb 2008 15:16:54 +0100
[EMAIL PROTECTED] wrote:
[PATCH 08/08]
This patch is the enhancement as asked for by Yasunori: if msgmni is set to
a negative value, register it back into the ipcns notifier chain.
A new interface has been added to the notification
[PATCH 03/08]
This is a trivial patch that defines the priority of slab_memory_callback in
the callback chain as a constant.
This is to prepare for next patch in the series.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/memory.h |6 ++
mm/slub.c |2
[PATCH 02/08]
Since all the namespaces see the same amount of memory (the total one)
this patch introduces a new variable that counts the ipc namespaces and
divides msg_ctlmni by this counter.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/ipc_namespace.h |1 +
ipc/msg.c
[PATCH 05/08]
This patch makes the memory hotplug chain's mutex held for a shorter time:
when memory is offlined or onlined a work item is added to the global
workqueue.
When the work item is run, it notifies the ipcns notifier chain with the
IPCNS_MEMCHANGED event.
Signed-off-by: Nadia Derbey
or an existing ipc namespace is
removed, the ipcns notifier chain is notified. The callback routine for each
registered ipc namespace is then activated in order to recompute msgmni for
that namespace.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/ipc_namespace.h | 25
.
Each callback routine registered in the ipcns namespace, in turn, recomputes
msgmni for the owning namespace.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/ipc_namespace.h | 43 -
include/linux/memory.h|1
ipc/Makefile
notifier chain.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
ipc/ipc_sysctl.c | 43 +--
1 file changed, 41 insertions(+), 2 deletions(-)
Index: linux-2.6.24-mm1/ipc/ipc_sysctl.c
it as a size in bytes (the code
expresses it in Kbytes).
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/msg.h | 14 --
ipc/msg.c | 37 -
2 files changed, 48 insertions(+), 3 deletions(-)
Index: linux-2.6.24-mm1/include
Resending the set of patches after Yasunori's remark about being able to
turn on/off automatic recomputing.
(see message at http://lkml.org/lkml/2008/2/5/149).
I actually introduced an intermediate solution: when msgmni is set by hand,
it is uneregistered from the ipcns notifier chain (i.e.
registered. With that new interface we avoid taking care of the states changes
in procfs.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/ipc_namespace.h |1
include/linux/notifier.h |4 +++
ipc/ipc_sysctl.c | 45
Yasunori Goto wrote:
Thanks Nadia-san.
I tested this patch set on my box. It works well.
I have only one comment.
---
ipc/ipc_sysctl.c | 43 +--
1 file changed, 41 insertions(+), 2 deletions(-)
Index: linux-2.6.24/ipc/ipc_sysctl.c
Pierre Peiffer wrote:
Nadia Derbey wrote:
[EMAIL PROTECTED] wrote:
From: Pierre Peiffer [EMAIL PROTECTED]
semctl_down() takes one unused parameter: semnum.
This patch proposes to get rid of it.
Signed-off-by: Pierre Peiffer [EMAIL PROTECTED]
Acked-by: Serge Hallyn [EMAIL PROTECTED
[PATCH 05/07]
This patche makes the memory hotplug chain's mutex held for a shorter time:
when memory is offlined or onlined a work item is added to the global
workqueue.
When the work item is run, it notifies the ipcns notifier chain with the
IPCNS_MEMCHANGED event.
Signed-off-by: Nadia Derbey
[PATCH 03/07]
This is a trivial patch that defines the priority of slab_memory_callback in
the callback chain as a constant.
This is to prepare for next patch in the series.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/memory.h |6 ++
mm/slub.c |2
Resending the set of patches after Yasunori's remark about having a single
callback on the hotplug memory notifier chain for the ipc subsystem.
(see thread at http://lkml.org/lkml/2008/1/14/196).
Cc'ing linux-mm since I'm adding a notifier block to the memory hotplug
notifier chain.
Also, Cc'ing
[PATCH 02/07]
Since all the namespaces see the same amount of memory (the total one)
this patch introduces a new variable that counts the ipc namespaces and
divides msg_ctlmni by this counter.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/ipc.h |1 +
ipc/msg.c
it as a size in bytes (the code
expresses it in Kbytes).
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/msg.h | 14 --
ipc/msg.c | 37 -
2 files changed, 48 insertions(+), 3 deletions(-)
Index: linux-2.6.24/include
notifier chain.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
ipc/ipc_sysctl.c | 43 +--
1 file changed, 41 insertions(+), 2 deletions(-)
Index: linux-2.6.24/ipc/ipc_sysctl.c
or an existing ipc namespace is
removed, the ipcns notifier chain is notified. The callback routine for each
registered ipc namespace is then activated in order to recompute msgmni for
that namespace.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/ipc.h | 25
.
Each callback routine registered in the ipcns namespace, in turn, recomputes
msgmni for the owning namespace.
Signed-off-by: Nadia Derbey [EMAIL PROTECTED]
---
include/linux/ipc.h| 38 ++
include/linux/memory.h |1
ipc/Makefile |3 +-
ipc
Resending with the right address for the containers mailing list.
So sorry...
Nadia Derbey wrote:
Hi,
Yesterday, I posted to lkml a series of patches that make the ipc
tunable msgmni scale with lowmem (see thread
http://lkml.org/lkml/2008/1/14/196).
Since these patches watch for memory
99 matches
Mail list logo
