[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121026110612.17494.95224.stgit@localhost.localdomain>
Date: Fri, 26 Oct 2012 15:06:12 +0400
From: Stanislav Kinsbursky <skinsbursky@...allels.com>
To: akpm@...ux-foundation.org
Cc: Larry.Finger@...inger.net, mitsuo.hayasaka.hu@...achi.com,
nhorman@...driver.com, linux-doc@...r.kernel.org,
catalin.marinas@....com, xemul@...allels.com, will.deacon@....com,
linux-kernel@...r.kernel.org, cmetcalf@...era.com,
dhowells@...hat.com, ebiederm@...ssion.com, rob@...dley.net,
dan@...dstab.net, tglx@...utronix.de, paulmck@...ux.vnet.ibm.com,
devel@...nvz.org, mtk.manpages@...il.com
Subject: [PATCH 4/5] Documentation: update sysctl/kernel.txt
This patch adds documentation about new "msg_next_id", "sem_next_id" and
"shm_next_id" sysctls.
Signed-off-by: Stanislav Kinsbursky <skinsbursky@...allels.com>
---
Documentation/sysctl/kernel.txt | 19 +++++++++++++++++++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index 2907ba6..51b953a 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@ -38,6 +38,7 @@ show up in /proc/sys/kernel:
- l2cr [ PPC only ]
- modprobe ==> Documentation/debugging-modules.txt
- modules_disabled
+- msg_next_id [ sysv ipc ]
- msgmax
- msgmnb
- msgmni
@@ -62,7 +63,9 @@ show up in /proc/sys/kernel:
- rtsig-max
- rtsig-nr
- sem
+- sem_next_id [ sysv ipc ]
- sg-big-buff [ generic SCSI device (sg) ]
+- shm_next_id [ sysv ipc ]
- shm_rmid_forced
- shmall
- shmmax [ sysv ipc ]
@@ -320,6 +323,22 @@ to false.
==============================================================
+msg_next_id, sem_next_id, and shm_next_id:
+
+These three toggles allows to specify desired id for next allocated IPC
+object: message, semaphore or shared memory respectively.
+
+By default they are equal to -1, which means generic allocation logic.
+Possible values to set are in range {0..INT_MAX}.
+
+Notes:
+1) kernel doesn't guarantee, that new object will have desired id. So,
+it's up to userspace, how to handle an object with "wrong" id.
+2) Toggle with non-default value will be set back to -1 by kernel after
+successful IPC object allocation.
+
+==============================================================
+
nmi_watchdog:
Enables/Disables the NMI watchdog on x86 systems. When the value is
--
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