Lines Matching +full:shared +full:- +full:memory

34 .Nd "shared memory object operations"
62 shared memory object named
84 then a new shared memory object named
88 the shared memory object is created with mode
95 flags are specified and a shared memory object named
104 If an existing shared memory object is opened with
109 then the shared memory object will be truncated to a size of zero.
129 In this case, an anonymous, unnamed shared memory object is created.
136 the shared memory object will be garbage collected when the last reference to
137 the shared memory object is removed.
138 The shared memory object may be shared with other processes by sharing the
143 Attempting to open an anonymous shared memory object with
157 object is always backed by aligned, physically contiguous chunks of memory.
158 This ensures that the object can be mapped using so-called
169 Largepage shared memory objects behave slightly differently from non-largepage
171 .Bl -bullet -offset indent
173 Memory for a largepage object is allocated when the object is
176 system call, whereas memory for regular shared memory objects is allocated
188 must be large page size-aligned, and the length of the operation must be a
214 to allocate memory for the object fails.
216 .Bl -tag -offset indent -width SHM_
218 If the (non-blocking) memory allocation fails because there is insufficient free
219 contiguous memory, the kernel will attempt to defragment physical memory and
229 If the memory allocation fails,
238 However, it is possible for physical memory to be fragmented such that the
247 commands can be used with a largepage shared memory object to get and set
250 .Bd -literal
268 works by creating a regular shared memory object using
276 system call atomically removes a shared memory object named
283 .Bl -tag -offset indent -width Er
297 system call removes a shared memory object named
302 function creates an anonymous shared memory object, identical to that created
334 .Bl -tag -width MFD_ALLOW_SEALING
352 both return a non-negative integer,
358 All functions return -1 on failure, and set
382 are guaranteed to access the same shared memory object if and only if
403 on a shared memory object, or on the descriptor returned by
414 also supports zero-copy transmission of data from shared memory
418 Neither shared memory objects nor their contents persist across reboots.
420 Writes do not extend shared memory objects, so
428 .Bd -literal -compact
448 .Bl -tag -width Er
475 .Bl -tag -width Er
492 was specified while creating an anonymous shared memory object via
508 is not specified and the named shared memory object does not exist.
513 are specified and the named shared memory object does exist.
519 and attempted to create a named shared memory object.
525 .Bl -tag -width Er
532 .Bl -tag -width Er
542 The shared memory object at
557 .Bl -tag -width Er
565 The named shared memory object does not exist.
569 requires write permission to the shared memory object.
591 .St -p1003.1b-93 .
604 The functions were reimplemented as system calls using shared memory objects