1 .\" Copyright (c) 1993 Luigi P. Bai (lpb@softint.com) July 28, 1993
3 .\" Permission is granted to make and distribute verbatim copies of this
4 .\" manual provided the copyright notice and this permission notice are
5 .\" preserved on all copies.
7 .\" Permission is granted to copy and distribute modified versions of this
8 .\" manual under the conditions for verbatim copying, provided that the
9 .\" entire resulting derived work is distributed under the terms of a
10 .\" permission notice identical to this one.
12 .\" Since the Linux kernel and libraries are constantly changing, this
13 .\" manual page may be incorrect or out-of-date. The author(s) assume no
14 .\" responsibility for errors or omissions, or for damages resulting from
15 .\" the use of the information contained herein. The author(s) may not
16 .\" have taken the same level of care in the production of this manual,
17 .\" which is licensed free of charge, as they might when working
20 .\" Formatted or processed versions of this manual, if unaccompanied by
21 .\" the source, must acknowledge the copyright and authors of this work.
23 .\" Modified Wed Jul 28 10:57:35 1993, Rik Faith <faith@cs.unc.edu>
24 .\" Modified Sun Nov 28 16:43:30 1993, Rik Faith <faith@cs.unc.edu>
25 .\" with material from Giorgio Ciucci <giorgio@crcc.it>
26 .\" Portions Copyright 1993 Giorgio Ciucci <giorgio@crcc.it>
27 .\" Modified Tue Oct 22 22:03:17 1996 by Eric S. Raymond <esr@thyrsus.com>
28 .\" Modified, 8 Jan 2003, Michael Kerrisk, <mtk.manpages@gmail.com>
29 .\" Removed EIDRM from errors - that can't happen...
30 .\" Modified, 27 May 2004, Michael Kerrisk <mtk.manpages@gmail.com>
31 .\" Added notes on capability requirements
32 .\" Modified, 11 Nov 2004, Michael Kerrisk <mtk.manpages@gmail.com>
33 .\" Language and formatting clean-ups
34 .\" Added notes on /proc files
36 .TH SHMGET 2 2006-05-02 "Linux" "Linux Programmer's Manual"
38 shmget \- allocates a shared memory segment
41 .B #include <sys/ipc.h>
42 .B #include <sys/shm.h>
44 .BI "int shmget(key_t " key ", size_t " size ", int " shmflg );
48 returns the identifier of the shared memory segment
49 associated with the value of the argument
51 A new shared memory segment, with size equal to the value of
53 rounded up to a multiple of
63 no shared memory segment corresponding to
76 and a shared memory segment already exists for
84 (This is analogous to the effect of the combination
94 to create a new segment.
95 If this flag is not used, then
97 will find the segment associated with \fIkey\fP and check to see if
98 the user has permission to access the segment.
101 used with \fBIPC_CREAT\fP to ensure failure if the segment already exists.
104 (least significant 9 bits)
105 specifying the permissions granted to the owner, group, and world.
106 These bits have the same format, and the same
111 Presently, the execute permissions are not used by the system.
113 .BR SHM_HUGETLB " (since Linux 2.6)"
114 Allocate the segment using "huge pages."
115 See the kernel source file
116 .I Documentation/vm/hugetlbpage.txt
117 for further information.
119 .BR SHM_NORESERVE " (since Linux 2.6.15)"
120 This flag serves the same purpose as the
124 Do not reserve swap space for this segment.
125 When swap space is reserved, one has the guarantee
126 that it is possible to modify the segment.
127 When swap space is not reserved one might get
130 if no physical memory is available.
131 See also the discussion of the file
132 .I /proc/sys/vm/overcommit_memory
135 .\" As at 2.6.17-rc2, this flag has no effect if SHM_HUGETLB was also
138 When a new shared memory segment is created,
139 its contents are initialized to zero values, and
140 its associated data structure,
144 is initialized as follows:
149 are set to the effective user ID of the calling process.
154 are set to the effective group ID of the calling process.
156 The least significant 9 bits of
158 are set to the least significant 9 bit of
162 is set to the value of
173 is set to the current time.
175 If the shared memory segment already exists, the permissions are
176 verified, and a check is made to see if it is marked for destruction.
178 A valid segment identifier,
180 is returned on success, \-1 on error.
184 is set to one of the following:
187 The user does not have permission to access the
188 shared memory segment, and does not have the
193 .B IPC_CREAT | IPC_EXCL
194 was specified and the segment exists.
197 A new segment was to be created and \fIsize\fP < \fBSHMMIN\fP
198 or \fIsize\fP > \fBSHMMAX\fP, or no new segment was to be created,
199 a segment with given key existed, but \fIsize\fP is greater than the size
203 .\" [2.6.7] shmem_zero_setup()-->shmem_file_setup()-->get_empty_filp()
204 The system limit on the total number of open files has been reached.
207 No segment exists for the given \fIkey\fP, and
212 No memory could be allocated for segment overhead.
215 All possible shared memory IDs have been taken
217 or allocating a segment of the requested
219 would cause the system to exceed the system-wide limit on shared memory
225 flag was specified, but the caller was not privileged (did not have the
230 .\" SVr4 documents an additional error condition EEXIST.
233 is a non-portable Linux extension.
236 isn't a flag field but a
239 If this special value is used for
241 the system call ignores everything but the least significant 9 bits of
243 and creates a new shared memory segment (on success).
245 The following limits on shared memory segment resources affect the
250 System wide maximum of shared memory pages
251 (on Linux, this limit can be read and modified via
252 .IR /proc/sys/kernel/shmall ).
255 Maximum size in bytes for a shared memory segment: policy dependent
256 (on Linux, this limit can be read and modified via
257 .IR /proc/sys/kernel/shmmax ).
260 Minimum size in bytes for a shared memory segment: implementation
261 dependent (currently 1 byte, though
263 is the effective minimum size).
266 System wide maximum number of shared memory segments: implementation
267 dependent (currently 4096, was 128 before Linux 2.3.99;
268 on Linux, this limit can be read and modified via
269 .IR /proc/sys/kernel/shmmni ).
270 .\" Kernels between 2.4.x and 2.6.8 had an off-by-one error that meant
271 .\" that we could create one more segment than SHMMNI -- MTK
272 .\" This /proc file is not available in Linux 2.2 and earlier -- MTK
274 The implementation has no specific limits for the per process maximum
275 number of shared memory segments
278 Until version 2.3.30 Linux would return
282 on a shared memory segment scheduled for deletion.
286 was perhaps unfortunate, IPC_NEW
287 would more clearly show its function.
293 .BR capabilities (7),